Skip to main content
Glama

authors-block

Destructive

Block author

Block an author with the built-in block action. A blocked author cannot post new content until unblocked.

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": {
      "request": "<request>"
    },
    "name": "authors-block"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

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?

Annotations already declare destructiveHint=true, readOnlyHint=false, non-idempotent and open-world behavior, so the safety profile is covered elsewhere. The description adds real context by stating the effect and its reversibility ('until unblocked'), but says nothing about what happens to existing content, whether repeat calls stack, or what error states occur when the author is already blocked.

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?

Two short sentences, front-loaded with the action and then the consequence; every sentence carries content. The only waste is the repeated 'Block author' heading echoed from the title, which adds nothing.

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 destructive mutation with a nested request object, no output schema, and several near-duplicate siblings, the description is thin. It never explains the nested 'request'/'body' envelope, the projectId scoping rules, or how 'block' differs from 'suspend', leaving the agent to reconstruct call shape and tool choice from the schema alone.

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 reported at 0% and the description supplies no parameter information at all. The tool takes a nested 'request' wrapper containing 'body' and 'id', and the description does not explain the envelope, the ID form, or how the optional 'reason' surfaces in webhooks — all of which the agent must infer from the schema.

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?

The description gives a specific verb and resource ('Block an author') and states the resulting state change ('cannot post new content until unblocked'), so an agent knows exactly what the call does. It does not differentiate from close siblings such as authors-suspend, authors-update or authors-delete, which prevents 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?

Usage is implied rather than stated: the effect sentence tells the agent this is the tool for stopping an author from posting. There is no explicit when-to-use guidance, no exclusion rules, and no mention of when authors-suspend or authors-delete would be the better choice.

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