Skip to main content
Glama
Sign In
Mnemento

Mnemento

by reddol18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_entity

Retrieve the current state of a single record after corrections and retractions, using its entity ID to get the up-to-date structured fact.

Instructions

Current state of one record (after corrections/retractions).

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/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 does disclose one meaningful trait — the returned state already reflects corrections/retractions — but says nothing about authentication, error behavior for unknown IDs, or read cost/rate limits.

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 fragment with no wasted words. It is efficient, though its brevity edges into under-specification rather than optimal concision.

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?

An output schema exists, so return-value explanation is not required, and the tool is simple with one parameter. However, in a crowded sibling namespace the description omits any routing signal that would let an agent distinguish it from query or history, leaving a real contextual gap.

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 schema provides no explanation of entity_id. The description mentions 'one record' but never explains the identifier's form or origin, adding essentially no meaning beyond the parameter 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 fragment 'Current state of one record' communicates the resource but supplies no action verb and no sibling differentiation. With 13 siblings including query, history, and record, an agent cannot easily tell why it would call get_entity over those alternatives. Purpose is inferable but vague.

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?

No when-to-use, when-not-to-use, prerequisites, or alternative tools are stated. The parenthetical about corrections/retractions hints at timing but provides no selection guidance against siblings like query or history.

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

Deploy Server

Other Tools