Skip to main content
Glama

GuestGraph

by io.guestgraph
OverviewDiscussionsAdmin

get_entity

Read-only

One entity as structured data: fields, sections, tables, references both ways. Use to reason over one; for its page as written use fetch. Input: id or address, where its page sits, or type and name; an ambiguous name is refused with candidate ids. Returns entity, by id. Reference lists hold at most 50 edges; referenceCounts gives totals, list_references the rest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe entity's id, as any answer gives it, or its address, where its page sits
nameNoThe canonical name, the entity's H1; needs type
typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
entityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / entity / properties / created
      Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The entity's id, as any answer gives it"New value: +"The entity's id, as any answer gives it, or its address, where its page sits"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral detail beyond them: ambiguous names are refused with candidate ids, reference lists are capped at 50 edges, referenceCounts supplies totals, and list_references is the escape hatch for the rest. That is exactly the extra context an agent needs to interpret a truncated result.

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?

Tight and front-loaded, with purpose first and the fetch contrast immediately after; no sentence is pure filler. The telegraphic em-dash style is dense to the point of being slightly clipped, but it earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need not be explained, yet the description still sketches the shape ('returns `entity`, by id') and covers the ambiguity refusal and the 50-edge truncation with its companion tool. Complete for the core call; a note on whether id/name/type can be combined would close the last gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 67% schema coverage the schema already documents id and name, but the description adds the id-or-address alternative and the type+name pairing for canonical-name lookup, plus the behavioral consequence of an ambiguous name. The bare `type` parameter is still not given standalone meaning.

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

Purpose5/5

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

States a concrete verb+resource: fetch 'one entity as structured data: fields, sections, tables, references both ways.' It also names a specific sibling (fetch) it must not be confused with, so an agent can separate the structured view from the rendered page without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the selecting condition ('Use to reason over one; for its page as written use fetch') and names the alternative, which is strong routing. It doesn't cover when to prefer list_entities or search instead, so it falls short of full when/when-not coverage.

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

All GuestGraph toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources