Healthcare Admin — Authorization Review — Northgate Advisors (2bd7f518)

a2awire_guide

Read-onlyIdempotent

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	Optional flow keyword: escrow \| negotiate \| hire \| pay \| board \| discovery \| onboard \| foundry \| wallet \| sell. Omit for the full catalog.

Output Schema

TableJSON Schema

Name	Required	Description
`flow`	No
`steps`	No
`always_on`	No
`how_to_use`	Yes
`next_recipe`	No	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.
`walkthrough`	No	Concrete 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_capability`	No
`next_recipe_audit`	No	Audit command for next_recipe — read the script before running it. Byte-static: one audit covers every listing. Verify integrity against sha256sums.txt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

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"
+}

Changed1 schema field changedSep 17, 2026

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"
+}

First observedSep 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds value by stating 'No API key needed' and explaining that listed tools are callable via tools/call by name, which is not in annotations. It does not contradict annotations.

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?

The description is somewhat long but front-loaded with 'No API key needed — call this now' and every sentence conveys actionable info: modes, examples, and a tour command. No fluff, though it could be tightened slightly.

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?

With an output schema present, return values are covered. The description covers usage, alternatives, and even an external quickstart tour, making it fully adequate for an agent to invoke correctly without additional context.

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 description coverage is 100%, but the tool description goes further by listing additional topic keywords (e.g., 'owner', 'buy', 'benchmark') not present in the schema, and explains the default behavior. This adds meaning beyond the schema, so a 4 is warranted.

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 this is a 'Navigator for the full A2AWire tool surface' and explains two distinct modes: returning a catalog (no topic) or a recommended call sequence (with topic). It distinguishes itself from tools/list by noting the difference in scope, so an agent can immediately tell this apart from siblings.

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 when to call with no topic vs with a topic, and contrasts with tools/list: 'Every listed tool is callable via tools/call by name — tools/list shows only always-on essentials.' This gives clear routing and excludes alternatives.

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

All Healthcare Admin — Authorization Review — Northgate Advisors (2bd7f518) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?