Skip to main content
Glama

case_graph

Map case entities and evidenced connections, optionally focused on one entity, to explain who is linked to whom and which claims remain leads.

Instructions

Return case entities and evidenced edges; optionally focus on one entity.

Mentions are separate from explicit facts. Use the returned IDs and source URLs to explain who is connected to whom and which claims remain leads.

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": {
      "case": "<case>"
    },
    "name": "case_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
limitNo
entityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose meaningful data semantics (mentions vs evidenced facts, returned IDs and source URLs usable for traceability). It does not state that the operation is read-only, what happens for an unknown case, or how results are truncated.

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 sentences, front-loaded with the core behavior, with no filler. The 'mentions are separate from explicit facts' line is terse but earns its place by flagging a data-model distinction.

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?

No output schema exists, so the description ideally would sketch the shape of entities and edges and explain the limit; it only gestures at usage of returned IDs and URLs. Adequate but clearly incomplete for a graph-returning tool with three undocumented-in-schema parameters.

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?

Schema coverage is 0%, so the description must compensate. It gives meaning to 'entity' (focus on one entity) and implicitly to 'case', but the 'limit' parameter (default 100) is entirely unaddressed, leaving truncation behavior undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Return case entities and evidenced edges', plus an optional single-entity focus. It is distinguishable from siblings such as case_search or case_list, though it does not name any alternative explicitly.

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?

'Optionally focus on one entity' implies when to supply the entity parameter, and the note about mentions versus explicit facts hints at how to read results. There is no explicit when-to-use/when-not guidance or routing to sibling tools like case_search.

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