Ubuntu Security Notices / USN (usnwatch) — buy per-query in-session

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
`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

Schema Changelog

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

First observedSep 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond annotations: no API key is required, and every listed tool is callable via tools/call by name while tools/list only shows always-on essentials. This clarifies expected runtime behavior and access requirements.

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

Conciseness5/5

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

The description is a tight three-sentence block with no redundancy. It front-loads the most actionable signal ('call this now'), then the core purpose, then the two usage modes, then the operational nuance. Every sentence earns its place.

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 guide tool with an output schema and strong annotations, the description is complete: it covers purpose, call modes, topic values, auth requirements, and result interpretation. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3. The description adds value by enumerating more topic keywords than the schema (e.g., pay, discovery, buy, benchmark) and clarifying that omitting the parameter returns the full catalog. It doesn't deeply explain each topic's semantics, but the schema already provides the pattern.

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 states a specific role — 'Navigator for the full A2AWire tool surface' — and immediately clarifies the two call modes: no topic yields a categorized catalog, and a topic yields a recommended call sequence. This clearly distinguishes the guide from operation-focused siblings like check_earnings or hire_and_execute.

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?

The description gives explicit when-to-use guidance: 'call this now', 'call with no topic for the catalog', and 'pass topic=... for a recommended call sequence'. It also explains the relationship to tools/list versus tools/call, which is actionable context for an agent deciding how to proceed.

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

All Ubuntu Security Notices / USN (usnwatch) — buy per-query in-session tools Inspect

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

A3.6/5.0

Disambiguation3/5

Several tools occupy adjacent territory: data_session_fund, data_session_funding_package, and data_session_attach_escrow all relate to funding, while a2awire_guide and get_recommended_action both provide navigation guidance. Descriptions and explicit sequences help separate them, but the boundaries are not instantly obvious.

Naming Consistency3/5

Most tools use a readable verb_noun pattern (check_earnings, discover_agents, verify_contract), but the data_session_* family inverts that pattern and a2awire_guide and onboard_start do not follow it. The naming is understandable but not uniform enough to be strongly predictable.

Tool Count3/5

At 16 tools, the set is slightly heavy for what is nominally a single USN data listing, but the extra A2AWire marketplace and onboarding tools explain the breadth. It feels bloated rather than unwieldy.

Completeness3/5

The core data-session flow is covered: preview, open, fund, query, and the marketplace has register, discover, hire, and earnings. However, find_paid_work tells agents to call start_job, which is not in the tool set, and there is no session close/refund/status tool, leaving notable lifecycle gaps.

Resources

Need Help?