Skip to main content
Glama

content-allow

Allow content

Allow a content item with the built-in allow action, and resolve it in the review queue.

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": "content-allow"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description does add one genuinely useful behavioral fact beyond that: the action resolves the item in the review queue, a side effect an agent would not infer from the annotations. It says nothing, however, about webhook events fired, casebook case creation, or that a repeated call is not idempotent.

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 with no filler, and the queue-resolution effect is placed where it will be read. The first line duplicates the tool title, which is the only waste.

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 mutation tool with no output schema, an agent still lacks the return shape, the failure modes, and whether the action can be undone (queue-items-unresolve exists as a sibling, hinting at reversibility that is never stated). The queue-resolution behavior is the main thing covered, which keeps it at minimum viable rather than inadequate.

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 top-level parameter is a nested request wrapper that the description never explains; the reported 0% coverage applies to that wrapper, though the nested id, reason, queueId, moderator and createCasebookCase fields are documented in the schema itself. The description therefore adds no meaning about required fields, defaults, or the projectId/organization-key interaction beyond what the schema already says.

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 verb and resource ("Allow a content item") but the opening line "Allow content" merely restates the tool name and title. The added clause "with the built-in allow action, and resolve it in the review queue" is the only real signal, and it implies the counterpart to content-reject without ever naming that sibling.

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 use this instead of content-reject, queue-items-resolve, or queue-items-resolve-many, all of which are close siblings. No prerequisites, no exclusions, no note that an allow decision is the terminal positive outcome of a review.

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