Skip to main content
Glama

scan_terms_of_service

Scan a terms-of-service / privacy-policy URL for risky clauses.

Call this BEFORE the agent accepts terms, creates an account, or grants a vendor access to the principal's data. Returns a risk score (0-100), a pass/flag/block verdict, and the top clauses with verbatim quotes. 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": {
      "url": "<url>"
    },
    "name": "scan_terms_of_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
policy_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 behavioral burden. It does disclose the return shape (0-100 risk score, pass/flag/block verdict, verbatim clause quotes) and adds a useful scope caveat ('informational assessment only — not legal advice'), but says nothing about live-fetch behavior, failure modes for unreachable URLs, latency, or whether results are persisted and retrievable via get_scan_report.

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?

Three short, front-loaded lines: what it does, when to call it, what comes back plus the disclaimer. No filler, and the action trigger precedes the output details where it matters most.

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 the return-value summary is arguably redundant, and the tool is a simple two-parameter read. The only meaningful gap for an agent deciding how to call it correctly 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.

Parameters2/5

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

Schema description coverage is 0%, so the schema documents neither parameter, and the description does not compensate. It hints at URL semantics by saying 'terms-of-service / privacy-policy URL', but policy_id — which appears to tie a scan to a stored policy, given siblings like create_policy and list_policies — is never explained at all.

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 opening line names a specific verb (scan), a specific resource (terms-of-service / privacy-policy URL), and the output dimension (risky clauses). It implicitly separates itself from scan_terms_text and batch_scan_terms by stating the input is a URL, but never names those siblings explicitly, so the differentiation is inferential rather than stated.

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?

The second sentence gives concrete triggering moments: before accepting terms, creating an account, or granting a vendor data access. That is real when-to-use guidance rather than a restatement of purpose. It stops short of when-not-to-use or naming an alternative tool for the text/batch variants.

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.