Spaces by Peakflo

graph_resolve

Read-only

Resolve an entity across systems. Find the golden record for a source entity, or look up by name/type. Returns the entity with all linked source records, relationships, and references.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_resolve"
  }
}

Input Schema

Name	Required	Description
`entity_id`	No	Direct entity ID lookup
`entity_type`	No	Filter by entity type when searching by name
`external_id`	No	External ID in the source system (use with source_system)
`name_search`	No	Search by entity name
`source_system`	No	Source system name (use with external_id)
`include_linked_datastores`	No	Include linked datastores for the entity and its relationships (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds what a caller actually gets back — the entity with its linked source records, relationships and references — which is meaningful context for a tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the core purpose first and the return contents second. No filler or redundancy.

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?

The description covers purpose and return shape, which matters given there is no output schema, but it omits resolution edge cases an agent would need: behavior on multiple matches, no match, or conflicting lookup modes. Adequate rather than complete.

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 description coverage is 100%, so every parameter is already documented, establishing a baseline of 3. The description hints at pairings (source entity vs name/type) but does not spell out the required combinations like external_id+source_system or name_search+entity_type, nor what happens when several parameters are supplied.

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?

The description states a specific verb and resource ('Resolve an entity across systems') and names the two resolution modes: golden-record lookup for a source entity, and lookup by name/type. It is clear what the tool does, though it never names a sibling (e.g. graph_entities) to mark the boundary.

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?

The two modes imply when each parameter set applies, which is more than nothing, but there is no explicit when-to-use guidance versus alternatives such as graph_entities or graph_linked_datastores, and no stated prerequisites or ordering.

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

All Spaces by Peakflo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.