Skip to main content
Glama

get_policies

Reads published terms of service and privacy policy as clause-level data to quote current wording and locate the clause that needs changes after a scan or audit.

Instructions

Call after scan_changes or audit to read the published terms of service and privacy policy, split into clauses (id, title, body, line). Use it to quote current wording and to locate the clause that needs to change. Requires .policy-drift.json.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonable work: 'read' signals a non-mutating operation, and it discloses a hard prerequisite ('Requires .policy-drift.json') plus the shape of what comes back. It does not say what happens if that file is absent or whether content is fetched live versus read from the local artifact, which keeps it from a 5.

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 sentences, zero filler, and the ordering constraint that determines correct invocation is front-loaded before the use cases. Every clause contributes information an agent needs.

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

Completeness5/5

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

For a zero-parameter read tool with no annotations and no output schema, the description covers the prerequisite, the call ordering, the return structure, and the intended downstream use. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical field list describes output, not inputs, and is not needed here but causes no confusion.

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 — reading the published terms of service and privacy policy — and specifies the unit of return (clauses with id, title, body, line). The opening clause about calling it after scan_changes or audit makes it distinguishable from the sibling scanning tools without opening any schema.

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 explicit sequencing ('Call after scan_changes or audit') and two concrete use cases: quoting current wording and locating the clause that needs to change. It stops short of an explicit when-not or a named alternative for conflicting use cases, so it lands just below the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.