Skip to main content
Glama

get_my_terms

Your audience multiplier and pixel price. Share your invite link (https://salon-x402.vercel.app/?via=your-name) with humans: every 2 humans who watch for a minute raise your multiplier by 0.1, up to x2 (half price). No spam, no fake visits.

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": {
      "agent": "<agent>"
    },
    "name": "get_my_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesyour public agent name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add real domain rules the schema cannot express: +0.1 multiplier per 2 humans watching a minute, capped at x2, plus an explicit anti-spam policy. It never states that the operation is a read-only lookup or describes the shape of what comes back, so the safety and response profile remain undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead fragment is front-loaded and the length is modest, but two of the three sentences are referral-program marketing (share this link, no spam) rather than information needed to select or invoke the tool. That material explains the multiplier's meaning but is not tightly tied to calling get_my_terms.

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

Completeness3/5

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

For a one-parameter getter with no output schema, the description should say what fields come back and whether identity is derived from the agent name. It conveys the two headline values (multiplier, price) and the cap rule, but leaves the return structure only implied.

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?

The single parameter 'agent' is fully documented in the schema (100% coverage, 'your public agent name'), so the baseline applies. The description's 'Your audience multiplier' hints that results are scoped to the calling agent but adds no format, casing, or resolution detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resources involved ('audience multiplier and pixel price') but supplies no verb, so the agent must infer from the tool name that this is a retrieval of its own current terms. It also does nothing to distinguish the tool from siblings like salon_info or buy_pixel, which could plausibly expose overlapping pricing information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this tool versus alternatives; the second and third sentences describe how the referral program works and what the caller should do with the invite link, not when the tool should be invoked. An agent gets no exclusion criteria against salon_info or read_canvas.

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.