Skip to main content
Glama

terms_check

Get a signed Act-Time Terms Receipt BEFORE acting on a service: what its terms said at this moment (risk score, agent-friendliness verdict, the verbatim clauses behind it), pinned to the terms document's hash and signed so anyone can verify it later — the evidence record for 'the agent checked before it acted'. Pass service for a published leaderboard service (e.g. 'discord') or url for any terms document. action optionally records what the agent was about to do (stored as caller-asserted; it is never witnessed). A receipt served from the board/cache costs no scan unit (monthly allowance); one that triggers a fresh scan consumes one.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
actionNo
serviceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses that the receipt is hash-pinned and signed for later verification, that the `action` field is caller-asserted and 'never witnessed', and that quota/scan-unit consumption depends on cache vs fresh scan. Missing pieces are auth requirements and error behavior when a terms document cannot be found or fetched.

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 core purpose and key properties before moving to parameter routing and cost, which is the right order for an agent deciding whether to call it. It is somewhat dense and em-dash-heavy, but each sentence contributes distinct information (contents, signing, parameter routing, quota model).

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?

An output schema exists, so return-value explanation is not owed, and the description covers purpose, all three parameters, trust semantics, and cost. Remaining gaps are cache staleness/expiry and failure behavior, which an agent would want when relying on a receipt as evidence. For a three-optional-parameter tool with no annotations, this is close to complete.

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?

Schema coverage is 0%, so the description must supply all meaning, and it does for all three parameters: `service` (published leaderboard service, example 'discord'), `url` (any terms document), and `action` (optionally records the pending action, stored as caller-asserted). It does not say how the two lookup parameters interact when both are supplied or what happens when neither is, which matters since all three are optional.

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?

States a specific verb and artifact: get a signed Act-Time Terms Receipt, with what it contains (risk score, agent-friendliness verdict, verbatim clauses) and how it is bound (pinned to the terms document hash, signed). It implicitly separates itself from sibling scan tools by framing the output as an evidence record rather than a scan, but it never names an alternative, so it falls short of full sibling differentiation.

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?

Gives a clear when: 'BEFORE acting on a service', and routing guidance between the two input modes ('Pass `service` for a published leaderboard service ... or `url` for any terms document'). It also implies a reuse preference by noting a cached receipt costs no scan unit while a fresh scan does. It stops short of explicit exclusions or naming a sibling tool to use instead when a full scan is wanted.

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.