Skip to main content
Glama

scan_terms_text

Scan pasted terms text (when no URL is available). Same contract as scan_terms_of_service: risk score, verdict, quoted clauses. Informational assessment only — not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "scan_terms_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
policy_idNo
source_urlNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral context — the returned contents (risk score, verdict, quoted clauses) and the important caveat "informational assessment only — not legal advice" — but it says nothing about side effects such as whether a scan is persisted (the policy_id parameter hints at storage), whether text size is limited, or cost/latency. Useful but incomplete for an unannotated tool.

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?

Three short sentences, front-loaded with the scope constraint, with no filler. The inventory of return fields is mildly redundant given an output schema exists, but it is brief and aids scanning.

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

Completeness3/5

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

The output schema covers return values, so that need is met, and the not-legal-advice disclaimer is a good addition. However, for a three-parameter tool with zero annotation and zero schema-description coverage, the description leaves policy_id and source_url entirely unexplained and does not note side effects like scan persistence.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters. The description only alludes to the required text input ("pasted terms text"); policy_id and source_url get no explanation of what they do, whether they associate the scan with an existing policy, or how source_url differs from the URL path of the sibling tool.

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?

"Scan pasted terms text" gives a specific verb and resource, and the parenthetical "(when no URL is available)" immediately separates it from scan_terms_of_service. An agent can pick this over the URL-based sibling without opening either schema.

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?

The selection condition is explicit and tied to the named alternative: use this when no URL is available (implying scan_terms_of_service otherwise). This is a clear use-case boundary rather than an implied one.

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.