Skip to main content
Glama

batch_scan_terms

Scan up to 20 vendor ToS URLs in one call; each scan costs one quota unit. Returns a ranking (riskiest first) with scores, verdicts, and top clause categories per vendor. Use this for vendor shortlists and bake-offs.

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": {
      "urls": "<urls>"
    },
    "name": "batch_scan_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
policy_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers the highest-value trait: the cost model ('each scan costs one quota unit') and the hard 20-URL cap. It does not address failure handling for a partially failing batch or whether scans are synchronous, which matters for a 20-item fan-out.

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?

Two tight sentences: scale and cost first, output shape second, intended use last. Every clause carries information (limit, quota, ranking order, return fields, use case) with no filler.

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?

With an output schema present, the description needn't enumerate return fields, and it still summarizes the ranking. Cost, batch limit, and use case are all covered, so an agent can call it correctly; the only real hole is the undocumented 'policy_id' parameter.

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 0%, so the description must compensate. It does well for 'urls' (vendor ToS URLs, max 20) but says nothing about 'policy_id' — what a policy is, whether it is optional, or what changes when it is set — leaving one of two parameters undocumented anywhere.

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?

States a specific verb and resource ('Scan ... vendor ToS URLs') plus the batch constraint ('up to 20 ... in one call'), which implicitly and clearly distinguishes it from a single-URL scan sibling. The returned artifact is also characterized (ranking, riskiest first), so an agent knows exactly what this produces.

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?

Explicitly names the intended scenario: 'Use this for vendor shortlists and bake-offs,' which tells the agent when this batch tool is the right pick over repeated single scans. It stops short of an explicit exclusion such as 'for a single URL use scan_terms_of_service,' so the when-not side is left to inference.

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.