Skip to main content
Glama

mocop

favorite_domain

Read-only

Follow 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": "favorite_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The description adds the authentication requirement, which the annotations do not cover, so it contributes beyond structured data. It says nothing about idempotency (what happens when the domain is already followed), whether the change is reversible, or where the result surfaces (e.g., list_favorites). Note the mild tension between "Follow" (a state-changing bookmark) and readOnlyHint=true; this reads as annotation looseness for a low-risk reversible favorite rather than a clear description-side contradiction.

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?

Eight words, front-loaded with the action, zero filler. Its brevity is not padding, though the same brevity is what creates the gaps scored elsewhere.

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

Completeness2/5

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

For a simple one-parameter tool with annotations and no output schema, an agent still lacks the input format for the only required argument and any statement of the effect's visibility/idempotency. The sign-in note helps, but the definition is thinner than the tool's minimal complexity requires.

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?

Schema description coverage is 0%, so the single domain parameter is undocumented everywhere. The description does not say whether domain means a bare hostname, a URL, or an internal identifier, nor whether it must be verified first — exactly the meaning the schema leaves out.

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?

"Follow a domain" pairs a specific verb with a specific resource and clarifies the synonym (favorite = follow), which is enough for an agent to tell it apart from unfavorite_domain without opening a schema. It stops short of naming any sibling explicitly, so it does not earn a 5.

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)" gives a real precondition for calling the tool, which is genuine usage context. However, there is no guidance on when to prefer this over add_domain/unfavorite_domain, no when-not condition, and no mention of what to do if already followed.

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