Skip to main content
Glama

Axint

by io.github.agenticempire

axint.registry.search

Read-onlyIdempotent

Search the Axint Registry for already-published packages that match a natural-language query. Use this BEFORE calling axint.feature or axint.compile so the agent can install an existing package instead of regenerating Swift the community has already shipped. Use: use before generating code to find reusable packages; not for validating local Swift. Inputs: query drives ranking; kind and platform narrow results without changing the registry source. Effects: read-only local registry search using AXINT_REGISTRY_PATH or sibling checkout; no network by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOptional surface filter.
limitNoHard cap on returned hits. Defaults to 10.
queryYesFree-form description of what the agent is about to build. E.g., 'log a workout', 'capture a voice note', 'show timer'.
minScoreNoMinimum normalized match score (0..1) below which results are dropped.
platformNoOptional platform filter. One of: iOS, macOS, watchOS, tvOS, visionOS.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Optional surface filter. One of: app-intent, view, widget, store, app, component. Loose match; 'intent'..."New value: +"Optional surface filter."
    • changedInput schema / properties / minScore / description
      Previous value: -"Minimum normalized match score (0..1) below which results are dropped. Defaults to 0.1."New value: +"Minimum normalized match score (0..1) below which results are dropped."
    • changedInput schema / properties / platform / description
      Previous value: -"Optional platform filter. One of: iOS, macOS, watchOS, tvOS, visionOS. Filters by the manifest's..."New value: +"Optional platform filter. One of: iOS, macOS, watchOS, tvOS, visionOS."
    • changedInput schema / properties / query / description
      Previous value: -"Free-form description of what the agent is about to build. E.g., 'log a workout', 'capture a voice note',..."New value: +"Free-form description of what the agent is about to build. E.g., 'log a workout', 'capture a voice note', 'show timer'."
    • removedOutput schema / properties / isError / description
      Removed value: -"Whether Axint marked the tool response as an error."
    • removedOutput schema / properties / text / description
      Removed value: -"Primary Axint tool response text, matching the first text content block."
  2. Changed4 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Optional surface filter. One of: app-intent,..."New value: +"Optional surface filter. One of: app-intent, view, widget, store, app, component. Loose match; 'intent'..."
    • changedInput schema / properties / minScore / description
      Previous value: -"Minimum normalized match score (0..1) below..."New value: +"Minimum normalized match score (0..1) below which results are dropped. Defaults to 0.1."
    • changedInput schema / properties / platform / description
      Previous value: -"Optional platform filter. One of: iOS,..."New value: +"Optional platform filter. One of: iOS, macOS, watchOS, tvOS, visionOS. Filters by the manifest's..."
    • changedInput schema / properties / query / description
      Previous value: -"Free-form description of what the agent is..."New value: +"Free-form description of what the agent is about to build. E.g., 'log a workout', 'capture a voice note',..."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: 'read-only local registry search using AXINT_REGISTRY_PATH or sibling checkout; no network by default.' This goes beyond annotations by describing the data source and network behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections for purpose, usage, inputs, and effects. Every sentence provides value, but there is slight redundancy ('Use this BEFORE...' and 'Use: use before...') that could be tightened. Still concise overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Has an output schema, so return format needs no description. The description covers purpose, when to use, exclusions, parameter semantics, and effects (none), making it fully complete for a read-only search tool. No significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds relational semantics: 'query drives ranking' and 'kind and platform narrow results without changing the registry source,' which clarifies how the parameters interact beyond their individual schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search the Axint Registry for already-published packages that match a natural-language query' — a specific verb, resource, and scope. It distinguishes itself from axint.feature and axint.compile by positioning itself as the pre-step for finding existing packages before generating code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this BEFORE calling axint.feature or axint.compile' and 'not for validating local Swift', giving clear when-to-use guidance and named alternatives. This leaves no ambiguity about when to prefer this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Axint toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with descriptions specifying exact use cases (e.g., axint.activate for smoke test, axint.status for version). There is minor potential overlap between axint.suggest and axint.feature, but descriptions clarify suggestion vs generation.

Naming Consistency5/5

All tools follow a consistent hierarchical pattern: 'axint.<category>.<action>' (e.g., axint.agent.advice, axint.swift.validate). Even standalone tools like axint.compile fit the pattern. No mixing of conventions.

Tool Count2/5

36 tools is well above the typical 3-15 range for a well-scoped set. While the server covers a broad domain, the sheer number may overwhelm agents and reduce efficiency. A reduction or grouping would improve coherence.

Completeness4/5

The tool set covers the full Axint development lifecycle: installation, compilation, validation, repair, upgrade, session management, and coordination. Minor gaps exist (e.g., no dedicated tool for deleting project artifacts), but core workflows are well-supported.

Resources