Skip to main content
Glama
Sign In
mapnotes

mapnotes

by joecabezas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get node

get_node
Read-only

Retrieve a single graph node, including its properties and every connected edge, by ID. Use it to inspect a node's details and relationships in a YAML or JSON graph.

Instructions

Return one node with its properties and all edges connected to it.

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": {
      "id": "<id>"
    },
    "name": "get_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
nodeYes
edgesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the retrieval scope (properties plus connected edges). It does not disclose behavior for a missing or invalid id (error vs empty result), which matters for a lookup tool, so it only clears the annotated bar partially.

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?

One sentence, front-loaded with the action and resource, with zero filler. Every clause carries information.

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 shape need not be restated. However, the zero-coverage id parameter and the undisclosed not-found behavior leave gaps that matter given the many sibling node tools an agent must choose between.

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% — the single 'id' parameter is documented nowhere, and the description never explains what identifier is expected (node key, name, UUID) or its format. With one required parameter and no compensating text, the description leaves the caller guessing.

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 ('Return') and resource ('node') and adds scope detail — properties plus all connected edges — which differentiates it from the plural search-style sibling find_nodes. It does not explicitly name any sibling to route against, so it stops short of a 5.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as find_nodes for lookup or get_graph for whole-graph retrieval. The agent must infer from the name alone whether this is the right call.

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