Skip to main content
Glama

Get Navigation Context

get_navigation_context
Idempotent

Returns the selected document, current address, and containing procedure in one provider-neutral result, so you can locate where the cursor sits even when no procedure applies.

Instructions

Return the selected document, current address, and containing/current procedure in one provider-neutral result. The result reflects sequential provider observations, not an atomic cursor snapshot; a cursor outside any procedure returns procedure: null.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
documentNoExact provider document or program identity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the result is a sequence of provider observations rather than an atomic cursor snapshot, and a cursor outside any procedure yields procedure: null. That tells the agent how to interpret inconsistency and edge cases. Minor tension remains: annotations set readOnlyHint=false while the description reads like a pure query, and no side effect is disclosed.

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?

Two tight sentences, front-loaded with the return payload and followed by the caveat about non-atomic observation. No filler, though the second sentence packs two distinct caveats together.

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?

With no output schema, the description carries the burden of describing return values and does so by naming the three result fields and the null-procedure case. It is nearly complete for a zero-required-parameter query tool, missing only guidance on when to prefer it over sibling context tools.

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% and the single optional 'document' parameter is documented in the schema as the exact provider document or program identity. The description never mentions the parameter, so it adds nothing beyond the schema; baseline 3 applies.

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 enumerates exactly what is returned: selected document, current address, and containing/current procedure, plus the provider-neutral framing. It does not explicitly differentiate itself from the sibling inspect_address_context, 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 Guidelines3/5

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

Usage is only implied by the returned fields — an agent can infer this is the tool for 'where am I right now' queries. There is no explicit when-to-use, when-not-to-use, or named alternative such as inspect_address_context.

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