Skip to main content
Glama

essay.gates

Validate an essay against read-only mechanical gates 1–11 and an unquoted-exact plagiarism blocker, returning blocking issues without conducting a review.

Instructions

Essay: essay.gates (read-only). Mechanical gates 1–11 and the unquoted-exact plagiarism blocker. This is not a review. The writer seat does not pass EQR here.

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": {
      "essay_id": "<essay_id>"
    },
    "name": "essay.gates"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
packNo
essay_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It asserts '(read-only)' and a seat-level restriction, which is useful, but says nothing about what the gates do on failure, whether results are persisted, whether body/pack override stored content, or what the caller receives. For a three-parameter gate tool with zero annotation coverage this is a substantial gap.

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?

Three short, front-loaded sentences with no filler; the read-only marker and the 'not a review' disambiguation come first. Brevity comes at some cost to clarity given the unexplained jargon, but nothing is redundant.

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?

With three parameters, no output schema, and no annotations, the description leaves out the two things an agent most needs: what body/pack mean and what a gate result looks like. The seat/EQR restriction is raised but never explained, so the definition is not self-sufficient for correct invocation.

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 description must compensate, and it does not — neither 'body' nor 'pack' is mentioned at all, leaving the agent to guess whether they supply the text to check, a pack of rules, or overrides. Only 'essay_id' is self-evident from its name.

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 identifies the resource as 'Mechanical gates 1–11 and the unquoted-exact plagiarism blocker', which tells an agent this runs deterministic checks rather than stylistic review. However, there is no explicit verb, and 'gates 1–11' and 'EQR' are internal jargon an outside agent cannot decode. It does partially separate itself from review-type tools, which helps.

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?

'This is not a review' and 'The writer seat does not pass EQR here' imply when this tool is and is not appropriate, and hint at a seat/permission constraint. The guidance is implied rather than explicit — no sibling (e.g. essay.revise) is named as the review alternative, and the EQR constraint is unexplained.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.