Skip to main content
Glama

Official Facts

official_facts
Read-onlyIdempotent

Read after front_door and before any payment. Returns the exact official facts served by the market: domain, deployment_commit (the exact 40-character Vercel commit SHA when supplied, otherwise null), Base network, USDC contract, treasury, fees, the current identity feature state, and the no-token statement. Merchant registration and key rotation stay browser-only for a human, through the first-party no-store https://1f3ea.com/join or https://1f3ea.com/rotate page, and are deliberately never an MCP tool. A declared coding_persistent or coding_ephemeral client with no browser instead uses POST /api/register or POST /api/rotate, with the same limits and unchanged save-first-then-re-enter proof. Browser signup downloads the key and eight recovery codes as two files made in the browser, then waits for "I saved both files". Browser rotation downloads only the replacement key and waits for its saved acknowledgement. No credential belongs in chat, an MCP tool argument, or an MCP tool result.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavior beyond that: deployment_commit is the exact 40-character SHA or null when unsupplied, and a hard rule that no credential may appear in chat, an MCP argument, or an MCP tool result. A large tail of the text concerns registration and rotation flows the tool does not perform, which dilutes the disclosure about this tool itself.

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 critical instruction and the return inventory are front-loaded, which is good structure. However, the second half drifts into detailed browser signup and rotation mechanics, including file downloads and the 'I saved both files' acknowledgement, which are not behaviors of this tool and inflate the definition considerably.

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

Completeness1/5

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

There is no output schema, so the description must explain return values; it does list them, which helps. But for a zero-parameter read tool with no annotations problems, the description is far longer than needed and spends most of its length on unrelated registration/rotation procedures instead of the facts it returns.

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

Parameters4/5

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

Zero-parameter tool, so the baseline is 4; the schema is empty with additionalProperties=false and there is nothing for the description to disambiguate. The text correctly implies no arguments are needed by describing a pure read of served facts.

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 names a specific verb-and-resource ('Read ... the exact official facts') and enumerates the returned fields: domain, deployment_commit, Base network, USDC contract, treasury, fees, identity feature state, no-token statement. That is clearly more than a restatement of the title. It stops short of distinguishing this tool from siblings such as treasury, which plausibly surfaces overlapping facts, so it is clear but not fully sibling-differentiated.

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?

Explicit sequencing guidance is front-loaded: 'Read after front_door and before any payment,' which tells the agent both the prerequisite and the trigger condition. It also routes non-browser clients to POST /api/register or POST /api/rotate rather than this tool. No explicit when-not-to-use clause for this tool itself, so not a 5.

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