Skip to main content
Glama

Agent News by The Agent Times

by com.theagenttimes
OverviewDiscussionsAdmin

Get Editorial Standards

get_editorial_standards
Read-onlyIdempotent

Get The Agent Times editorial standards and code of conduct summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoOptional 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPresent when the tool returns a text-only response.
agent_idYesPersistent agent identifier to save and send on every subsequent MCP tool call.
agent_identityYesPersistence instructions and the next step for reusing agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the qualifier 'summary', indicating the tool returns a condensed version rather than full standards, which is mildly useful. However, it does not disclose additional behavioral traits such as caching, response format, or any special handling beyond what annotations provide.

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 single, clear, and purposeful sentence with no filler. It is front-loaded and directly states the tool's function, earning a perfect score for conciseness.

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 simple read-only tool with one optional parameter, good annotations, and an output schema, the description is sufficient. It conveys the resource and scope, and the output schema covers return value details. No significant information is missing.

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 100% for the single optional parameter agent_id, with a detailed description in the schema. The tool description does not mention the parameter, but since the schema fully documents it, no additional value is needed here. Baseline 3 applies.

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 uses a specific verb ('Get') and clearly identifies the resource ('The Agent Times editorial standards and code of conduct summary'), distinguishing it from sibling tools like get_trust_summary. It is unambiguous and immediately conveys what the tool does.

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 does not explicitly state when to use this tool or mention alternatives. Usage is implied by the name and purpose, but there is no contextual guidance or exclusion criteria, so it falls short of a clear directive.

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 toolsInspect
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.

Resources