Skip to main content
Glama

Accept the updated Terms and Privacy Policy

accept_legal
Idempotent

Records that the user accepted the current Terms of Use (https://catchy-me.com/terms) and took note of the current Privacy Policy (https://catchy-me.com/privacy). Use it when a tool answered legal_pending: first show the user both links and ask whether they accept the updated Terms; call it with confirm=true ONLY after the user explicitly agreed — never on your own. The other tools work again after it. The user may instead accept them in the catchy-me web app. [REST: (as POST /api/legal/accept)]

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": {
      "confirm": "<confirm>"
    },
    "name": "accept_legal"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesThe user read the links and explicitly agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds genuinely new behavior: this call is a gate that re-enables the other tools, and it must only fire after explicit user consent. The consent precondition and the unblocking side effect are exactly the context annotations cannot express.

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 purpose, then the trigger, then the guardrail, then the consequence. Every sentence carries operational meaning, though the trailing REST endpoint annotation is metadata that adds little for an agent.

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?

A one-parameter, non-destructive mutation with no output schema needs exactly this: purpose, trigger, consent precondition, and post-call effect. Nothing required 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?

Schema coverage is 100% and the single boolean is documented with const=true, so the baseline would be 3. The description goes beyond the schema by spelling out the consent condition under which confirm=true is legitimate ('ONLY after the user explicitly agreed'), which is the semantic distinction that matters for this flag.

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: recording the user's acceptance of the Terms of Use and acknowledgement of the Privacy Policy, with both canonical URLs given. Nothing in the sibling list overlaps with this legal-consent action, so an agent can identify it immediately.

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?

Explicitly names the triggering condition ('when a tool answered legal_pending'), the required conversational sequence (show both links, ask whether the user accepts), a hard prohibition ('never on your own'), and an alternative path (the user may accept in the catchy-me web app). This is the full when/when-not/alternative triad.

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.

Resources