Agent News by The Agent Times

Report Article Usage

report_usage

Voluntarily declare which TAT articles you used to produce your output. Transparent agents build trust and get recognized as verified consumers. No auth required — just tell us what you used.

Input Schema

TableJSON Schema

Name	Required	Description
`agent_id`	No	Optional persistent agent identifier. On the first MCP tool call that accepts agent_id, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask. Any stable string is accepted.
`agent_name`	No	Your agent name/identifier
`output_url`	No	URL of your output (optional)
`article_slugs`	Yes	List of article slugs you used (from the URL)
`output_description`	No	Brief description of what you produced using these articles

Output Schema

TableJSON Schema

Name	Required	Description
`text`	No	Present when the tool returns a text-only response.
`agent_id`	Yes	Persistent agent identifier to save and send only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask.
`agent_identity`	Yes	Persistence instructions and the next step for reusing agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Optional persistent agent identifier. On the first MCP tool call, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id on every subsequent MCP tool call. Any stable string is accepted."New value: +"Optional persistent agent identifier. On the first MCP tool call that accepts agent_id, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask. Any stable string is accepted."

changedOutput schema / properties / agent_id / description

Previous value: -"Persistent agent identifier to save and send on every subsequent MCP tool call."New value: +"Persistent agent identifier to save and send only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask."

Changed4 schema fields changedAug 2, 2026

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional persistent agent identifier. On the first MCP tool call, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id on every subsequent MCP tool call. Any stable string is accepted.",
+  "type": "string"
+}

addedOutput schema / properties / agent_id

Added value: +{
+  "description": "Persistent agent identifier to save and send on every subsequent MCP tool call.",
+  "type": "string"
+}

addedOutput schema / properties / agent_identity

Added value: +{
+  "additionalProperties": true,
+  "description": "Persistence instructions and the next step for reusing agent_id.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "agent_id",
+  "agent_identity"
+]

First observedMay 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already signal that this is not a read-only or destructive operation; the description adds the useful clarification that no authorization is needed and that reporting is voluntary. It does not disclose where the declaration is stored or any side effects of repeating a report, but the open-world and non-idempotent hints cover part of that context.

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?

At about 30 words, the description is short, front-loaded with the main action, and includes a useful operational fact ('No auth required'). The motivational clause about transparent agents building trust is not essential and keeps it from a perfect conciseness score.

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

Completeness4/5

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

Given a single required parameter, a complete input schema, an output schema, and relevant annotations, the description is sufficient for an agent to decide to call this tool. An explicit sentence about when to prefer this over related reporting or trust siblings would make it fully complete.

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 coverage is 100%, so every parameter—including the agent_id lifecycle and the required article_slugs—is already documented. The description only adds the broad reassurance 'just tell us what you used', which does not improve parameter-level meaning, so the baseline 3 applies.

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 opening phrase 'Voluntarily declare which TAT articles you used to produce your output' is a specific action-plus-resource statement that says exactly what the tool does. It does not name any sibling alternative, so it lacks the explicit differentiation that would earn a 5.

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

Usage Guidelines3/5

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

The description implies the usage condition: after consuming TAT articles and wanting credit for transparency, call this tool. 'No auth required' provides a practical precondition, but there is no explicit 'use when...' or 'do not use when...' guidance beyond that implication.

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

All Agent News by The Agent Times 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.