Skip to main content
Glama

A2A agent card validator

submit_a2a_card_validator
Idempotent

Validate an A2A agent card, report every missing field, and deliver a repaired copy. Before publishing an A2A agent card. Do not choose this when you need the agent's endpoints exercised. Example requests: Validate this A2A agent card. | Is my agent card complete for A2A discovery? | Fix the missing fields in this agent card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_a2a_card_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already carry the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=false), and the description usefully adds that a repaired card is produced, not just a verdict. However, it says nothing about the priced-capability flow implied by quote_id and accepted_price, nor that this is an authorization-gated job, which is significant behavior for a submit_* tool. It also never clarifies whether the repaired copy is written anywhere or only returned.

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

Conciseness3/5

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

The core capability is front-loaded, but 'Before publishing an A2A agent card.' is an ungrammatical fragment that costs a sentence without adding clear guidance. The three example requests largely restate the first sentence and add bulk rather than disambiguation.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the validation purpose is covered. What is missing is context for a four-parameter, authorization-and-quote-driven job tool: nothing tells the agent that a quote may be required before submitting or how accepted_price interacts with it. The description is adequate for the validation aspect but incomplete for the invocation mechanics.

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

Parameters3/5

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

Schema description coverage is 75%, with card, quote_id, accepted_price, and authorized_by all documented inline, so the schema does most of the work. The description adds no parameter-level meaning beyond implying the card is text input. Baseline 3 is appropriate given the coverage level.

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 gives a specific verb and resource plus three concrete outcomes: validate an A2A agent card, report every missing field, and deliver a repaired copy. That is clearly distinguishable from generic validators like submit_json_schema_validation because the resource is named. It stops short of a 5 because it never names a sibling tool it overlaps with, relying instead on a loosely worded exclusion.

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

Usage Guidelines4/5

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

It states a positive trigger ('Before publishing an A2A agent card') and an explicit negative one ('Do not choose this when you need the agent's endpoints exercised'), which is real when/when-not guidance. The exclusion is vague about which tool does exercise endpoints, so the agent must infer the alternative from the sibling list.

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