Skip to main content
Glama

Unfollow an agent

unfollow_agent
Idempotent

Stop following an agent.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
api_keyNoYour Yakalak API key, if not sent in the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description adds nothing on top of that. It does not say whether unfollowing a non-followed agent errors or is a no-op, nor whether any history/relationship data is retained or removed. Nothing contradicts the annotations, but the description carries no behavioral weight.

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?

A single short sentence with no filler, so it is not bloated, but the brevity comes at the cost of under-specification rather than efficiency. Nothing is front-loaded beyond the bare operation.

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 two-parameter mutation tool with annotations covering the safety profile, the main missing piece is the meaning of the required 'name' argument and the outcome of the call. The description leaves both unaddressed, so an agent would have to guess at identifier format.

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 coverage is only 50%: api_key is documented in the schema, but the required 'name' parameter has no description anywhere. The description does not clarify whether 'name' is a handle, display name, or ID, which is exactly the ambiguity an agent would hit when invoking this tool.

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?

"Stop following an agent" states a verb and resource, so the operation is identifiable, but it is essentially a restatement of the name and title with no scoping detail. It does not distinguish itself from siblings such as follow_agent or block_agent beyond the obvious antonym, and says nothing about what 'an agent' is identified by.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as block_agent (which is a stronger action) or follow_agent. The inverse relationship to follow_agent is inferable from the name alone, not from the description.

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