Skip to main content
Glama

submit_review

Submit evidence and a review result for an exact leased revision so reviewers can validate the intended knowledge entry version.

Instructions

Submit evidence and a result for an exact leased revision.

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": {
      "entry_id": "<entry_id>",
      "revision_id": "<revision_id>",
      "result": "<result>",
      "method": "<method>"
    },
    "name": "submit_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo
methodYes
resultYes
entry_idYes
evidenceNo
lease_idNo
conditionsNo
limitationsNo
revision_idYes
actor_handleNo
evidence_classNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about mutation semantics, permissions, lease validation failure modes, or idempotency despite an idempotency_key parameter existing. The only behavioral hint is the word 'leased', which weakly implies optimistic concurrency but is never explained.

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?

A single front-loaded sentence with no filler, so nothing is wasted. Its brevity is a symptom of under-specification rather than verbosity, which is penalized elsewhere rather than here.

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 12-parameter mutation-style tool with zero annotation coverage and no field documentation, this is far too thin; the existence of an output schema excuses it from explaining return values, but not from explaining lease acquisition, required-vs-optional field meaning, or idempotency behavior.

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% across 12 parameters, so the description must compensate and does not. It gestures at evidence, result, and revision_id, but leaves method, entry_id, lease_id, evidence_class, conditions, limitations, actor_handle, idempotency_key, and job_id entirely unexplained in both schema and description.

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?

States a verb (submit) and the payload (evidence + result) scoped to 'an exact leased revision', which gives some precision about which revision is targeted. However, 'review' is never defined and nothing distinguishes this from siblings like record_outcome or upload_evidence, so an agent cannot infer the boundary of the action from the sentence alone.

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 precondition (must a lease be held first?), no exclusions, and no named alternative among siblings such as record_outcome or propose_revision. The phrase 'exact leased revision' implies a lease must already exist but never says so explicitly.

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