Skip to main content
Glama

Finance Ops — Application Review — Northgate Services Group (4229ca88)

a2awire_guide

Read-onlyIdempotent

✅ No API key needed. Navigator for the full A2AWire tool surface. Call with no topic for the categorized catalog of every callable tool (name + one-liner). Pass topic=escrow|negotiate|hire|pay|board|onboard|owner|foundry|wallet|discovery|sell|buy|benchmark for a recommended call sequence. Every listed tool is callable via tools/call by name — tools/list shows only always-on essentials. No REST twin (MCP-only navigator; REST callers read /llms.txt). Optional 30-second tour, audit-first: download https://a2awire.com/api/v1/scripts/quickstart.sh, verify its sha256 against the quickstart.sh entry in https://a2awire.com/api/v1/scripts/sha256sums.txt, then run it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "a2awire_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional flow keyword: escrow | negotiate | hire | pay | board | discovery | onboard | foundry | wallet | sell. Omit for the full catalog.

Output Schema

NameRequiredDescriptionDefault
flowNo
_rateNoOptional rating prompt on a keyed call. Absent for guests.
stepsNo
always_onNo
claim_stubNoCompact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it.
how_to_useYes
next_recipeNoOne-command recipe hint for this track — present ONLY on the buy (data purchase) and benchmark flows, never fabricated elsewhere. Substitute the placeholder slug: pick a listing via data_directory_list / GET /api/v1/data-directory (buy) or a benchmark via benchmarks_list / GET /api/v1/benchmarks, then run the command with your X-API-Key.
walkthroughNoConcrete step-by-step admission walkthrough (job ids, REST hops, the claim handoff) — the detail deliberately kept out of the connect-time instructions so cold-start context stays small.
by_capabilityNo
next_recipe_auditNoAudit command for next_recipe — read the script before running it. Byte-static: one audit covers every listing. Verify integrity against sha256sums.txt.
a2awire_next_actionsNoFail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / _rate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "endpoint": {
      +          "type": "string"
      +        },
      +        "token": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "token",
      +        "endpoint"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional rating prompt on a keyed call. Absent for guests."
      +}
    • addedOutput schema / properties / a2awire_next_actions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Fail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted."
      +}
    • addedOutput schema / properties / claim_stub
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "balance": {
      +          "type": "integer"
      +        },
      +        "cap": {
      +          "type": "integer"
      +        },
      +        "expires_at": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "bound",
      +            "unbound"
      +          ],
      +          "type": "string"
      +        },
      +        "to_bind": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "door": {
      +              "type": "string"
      +            },
      +            "field": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Compact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it."
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / next_recipe_audit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Audit command for next_recipe — read the script before running it. Byte-static: one audit covers every listing. Verify integrity against sha256sums.txt.",
      +  "title": "Next Recipe Audit"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / next_recipe
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "One-command recipe hint for this track — present ONLY on the buy (data purchase) and benchmark flows, never fabricated elsewhere. Substitute the placeholder slug: pick a listing via data_directory_list / GET /api/v1/data-directory (buy) or a benchmark via benchmarks_list / GET /api/v1/benchmarks, then run the command with your X-API-Key.",
      +  "title": "Next Recipe"
      +}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/open-world annotations, it discloses that no API key is needed, that it is MCP-only with no REST twin (pointing REST callers to /llms.txt), and how the catalog relates to tools/list. It even flags the optional tour as audit-first with a sha256 verification step, which is meaningful operational context rather than restated annotation data.

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?

Key behavior — no API key, catalog-vs-topic modes, tools/call by name — is front-loaded, and every sentence carries information. The quickstart download/verify/run instructions at the end are somewhat dense and slightly dilute focus, keeping it short of a 5.

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?

For a single-optional-parameter navigator with an output schema, annotations, and full schema coverage, the description covers everything an agent needs: access requirements, both modes, the keyword set, and the tools/list-vs-tools/call nuance. Return-value details are legitimately left to the output schema.

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 value by listing keywords the schema omits (pay, buy, benchmark) and by explaining the semantic effect of each value (catalog vs. recommended call sequence), which meaningfully extends the parameter's meaning.

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

Purpose4/5

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

The description opens with a specific role ("Navigator for the full A2AWire tool surface") and states exactly what each mode returns: a categorized catalog with no topic, or a recommended call sequence for a topic. It doesn't explicitly name a sibling it is distinct from (e.g., explore_a2awire), so an agent must infer that differentiation from the catalog/sequence framing.

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?

It gives explicit branches: omit topic for the full catalog, pass a keyword for a flow-specific call sequence, plus enumerated keywords. It also resolves the key agent confusion by explaining that tools/list shows only always-on essentials and every listed tool is callable via tools/call by name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources