Skip to main content
Glama

mocop

get_entity_versions

Read-only

Version history of an entity, or the changes in one version.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
versionNo

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no ordering of versions, no pagination or result-size behavior, no indication of what happens when the version does not exist, and no note on whether the two modes return different shapes.

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 short sentence with no filler, and the two-mode distinction is front-loaded. The brevity is close to the point of under-specification rather than verbosity, but nothing in the text is wasted.

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 no output schema, 0% parameter coverage, and only minimal annotations, the description should explain the identifier format, version ordering, and what each mode returns. None of that is present, so an agent cannot confidently invoke it or interpret the result.

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 carries the full burden. It does clarify that the optional version parameter switches from history to a single version's changes, which is genuinely useful. But slug is never explained (entity identifier? format?), leaving the required parameter undocumented 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?

The description names the resource (an entity's version history) and distinguishes two modes: full history versus the changes in a single version. However, it is a noun phrase with no verb ('returns', 'lists'), so the agent must infer that this is a read/retrieval tool, and it does not differentiate itself from the sibling get_entity.

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 explicit when-to-use guidance, no statement of when to prefer get_entity over this tool, and no prerequisites or exclusions. The only usage signal is implicit: omitting version yields history, supplying it yields one version's changes.

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