Gomo Sounds

Accept the Terms of Use

accept_terms

Idempotent

Accepts the current Terms of Use and Privacy Policy for the account, like the button on the site. Call it ONLY after a tool answered terms_required, you asked the user that exact question with the links and the user explicitly said yes in this conversation. Never call it on your own or because the user asked for something else. Then retry what you were doing.

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": {
      "accepted": "<accepted>"
    },
    "name": "accept_terms"
  }
}

Input Schema

Name	Required	Description	Default
`accepted`	Yes	true only when the user said yes to accepting.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations supply only idempotentHint=true, and the description adds real behavioral context: this is a consent action gated on a prior terms_required signal, requires user-in-the-loop confirmation, and has a defined follow-up (retry the interrupted action). It does not say what happens if the call fails or the user declines, which keeps it short of 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 tight sentences, front-loaded with the precondition that matters most, and every clause carries operational weight (trigger, confirmation requirement, prohibition, follow-up). No filler or repetition.

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 one-parameter, no-output-schema consent gate, the definition covers everything an agent needs: the trigger, the confirmation ritual, the prohibition, and the post-call behavior. Nothing essential is left unspecified.

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 coverage is 100% and the single boolean already documents "true only when the user said yes to accepting." The description reinforces the consent semantics of that flag but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 ("Accepts the current Terms of Use and Privacy Policy for the account") and anchors it with a concrete analogy ("like the button on the site"). It is unmistakable which action is performed and no sibling tool could be confused with it.

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?

Gives explicit preconditions and exclusions: call ONLY after a tool returned terms_required, after asking the user the exact question with links, and after an explicit yes. It also states when NOT to call ("Never call it on your own or because the user asked for something else") and what to do afterwards ("retry what you were doing").

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

All Gomo Sounds tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?