A2UI Atomic Catalog

identify_model

Read-onlyIdempotent

CALL THIS FIRST, before any other a2ui-catalog tool, once per session. Declares your own model identity so this response can hand you capability-matched guidance up front — some models need simpler, judgment-free tools; skipping this just means you default to the full toolkit, including tools that require sizing/pagination judgment calls.

HOW TO ANSWER — do not guess:

Copy your model name EXACTLY as stated in your own system prompt or developer context (look for phrasing like "you are powered by the model named X" or similar). Do NOT infer it from your training cutoff, your own behavior, or general capability.
Examples of valid values: "claude-haiku-4-5", "claude-sonnet-5", "claude-opus-4-8", "gemini-2.0-flash", "gpt-4o". Partial names are fine ("haiku", "sonnet").
If your model name is genuinely not stated anywhere in your context, pass "unknown" — do NOT guess a plausible-sounding value. A wrong report is worse than no report: it can hand you tools you cannot reliably operate.

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": {
      "model": "<model>"
    },
    "name": "identify_model"
  }
}

Input Schema

Name	Required	Description	Default
`model`	Yes	Your own model identifier, exactly as your system prompt states it, or "unknown" if not stated. Do not guess.

Output Schema

Name	Required	Description
`tier`	Yes	Capability tier.
`guidance`	Yes	Capability-matched advice.
`recognized_as`	Yes	Model name as declared, lower-cased, or "unknown".
`recommended_tools`	Yes	Tool names to prefer.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, but the description adds real operational context: the call shapes which other tools get surfaced, the frequency is once per session, and an incorrect report has downstream cost ('A wrong report is worse than no report'). It does not describe what the response looks like, though an output schema exists, so that omission is minor.

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?

Front-loaded with the imperative and the routing rule, then a clearly delimited 'HOW TO ANSWER' block with bullets. A few clauses are somewhat redundant (restating the guessing warning in both the bullet and the closing sentence), but no sentence is off-topic.

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?

Low complexity, one fully documented parameter, annotations present, and an output schema so return values needn't be explained. Everything an agent needs to call this correctly on the first attempt is present.

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

Parameters5/5

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

Schema coverage is 100% and there is only one parameter, yet the description still adds substantive meaning: how to locate the value in the system prompt, what phrasing to look for, examples of valid formats, that partial names are acceptable, and a safe fallback. This is meaning an agent could not get from the schema alone.

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?

States a specific verb and resource ('Declares your own model identity') plus the downstream benefit ('capability-matched guidance up front'), and explicitly anchors it as the first call before any other a2ui-catalog tool. No sibling offers this function, so the agent can route to it unambiguously.

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?

Gives explicit when-to-use ('CALL THIS FIRST', 'once per session') and an explicit consequence for skipping ('you default to the full toolkit, including tools that require sizing/pagination judgment calls'). It also preempts the wrong behavior with a stated fallback ('pass "unknown" — do NOT guess').

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

All A2UI Atomic Catalog 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.