A2UI Atomic Catalog

get_profile

Read-onlyIdempotent

Read the signed-in reader's saved profile and recent history. Call this BEFORE asking a runbook's elicit questions: if a domain or default lens is already saved, CONFIRM it ("reading as: a2ui, generative ui — change?") instead of asking from scratch. Returns available:false on the public endpoint, where there is no one to have a profile — that is the designed state, so degrade quietly and just ask the questions.

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": "get_profile"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No	Guidance for the caller.
`user`	No	The reader {sub, email}.
`reason`	No	Why it is unavailable.
`profile`	No	Saved profile fields.
`greeting`	No	Display name or "you".
`available`	Yes	False when there is no signed-in reader or the store failed.
`total_readings`	No	Total saved readings.
`recent_readings`	No	Most recent readings.
`display_name_set`	No	Whether a display name is saved.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes beyond them by disclosing the designed failure mode: available:false on the public endpoint, with guidance to degrade quietly. That is exactly the kind of edge-case context annotations cannot express.

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?

Three sentences, front-loaded with the verb+resource, then the when-to-call rule, then the degraded-state caveat. The inline example wording ("reading as: a2ui, generative ui — change?") is short and directly actionable rather than filler.

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 parameterless read tool with an output schema and full annotation coverage, the description supplies the only missing pieces: when to invoke it in a runbook flow and how to handle the public-endpoint case. Nothing an agent needs in order to call it correctly is absent.

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?

Zero parameters, so the baseline is 4, and the description adds nothing contradictory or redundant about inputs. It does supply the one semantic an agent needs in lieu of parameters: the response can carry available:false, which changes how the result must be interpreted.

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?

Specific verb+resource ("Read the signed-in reader's saved profile and recent history") with an explicit actor scope (the signed-in reader). This cleanly separates it from the write-side sibling save_profile and from the content-oriented siblings like list_readings.

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 an explicit call-order instruction ("Call this BEFORE asking a runbook's `elicit` questions") plus the action to take with the result (confirm an already-saved domain/lens rather than re-asking). It also names the condition under which the tool is not useful (the public endpoint, where there is no signed-in reader).

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.