Skip to main content
Glama

mocop

unfavorite_domain

Read-only

Stop following a domain (requires sign-in).

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": {
      "domain": "<domain>"
    },
    "name": "unfavorite_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The operation removes a domain from the caller's follow/favorites list, i.e. it persists a change to user state, yet annotations declare readOnlyHint=true. The description's mutation semantics directly conflict with the read-only annotation, which will mislead an agent deciding whether a call is side-effect free.

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?

One short sentence, front-loaded with the action and resource, with the precondition parenthetically appended. There is no wasted wording, though the parenthetical could carry more than just sign-in.

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 trivial single-parameter tool without an output schema, the description covers the action and the auth requirement. It is still missing the parameter format and the idempotency/failure behavior an agent needs to call it confidently.

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?

There is a single required parameter with 0% schema description coverage, and the description says nothing about its expected form (bare domain name vs. URL vs. identifier) or case sensitivity. The description leaves the only input entirely undefined.

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?

"Stop following a domain" states a specific verb and resource and clearly contrasts with favorite_domain and add_domain in the sibling set. It stops short of naming the counterpart tool, but the action is unambiguous to an agent.

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

Usage Guidelines3/5

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

The parenthetical "(requires sign-in)" communicates a precondition, which is useful. However, there is no explicit guidance on when to prefer this over favorite_domain or how to handle domains that are not currently followed (error vs no-op).

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