Skip to main content
Glama
Sign In
arcgis-docs

arcgis-docs

by GeorgeSuarez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get an ArcGIS docs page

get_page
Read-onlyIdempotent

Retrieves indexed Markdown content for an ArcGIS documentation URL returned by search_docs, truncating long pages to a specified character limit.

Instructions

Return the indexed Markdown content for a documentation URL. Use a URL returned by search_docs. Long pages are truncated to maxChars.

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": {
      "url": "<url>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL returned by search_docs.
maxCharsNoMaximum characters of Markdown to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: content is indexed Markdown (not raw HTML/rendered output) and long pages are silently truncated to maxChars, which affects what the agent receives.

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 purpose and no filler. The truncation note is placed last where it reads naturally as a caveat.

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?

For a two-parameter read tool with full schema coverage and annotations covering safety, the description covers what is returned (Markdown, possibly truncated) and where the URL must come from. Error behavior for non-indexed or invalid URLs is the main unaddressed case, but no output schema exists so return-format explanation is appropriately handled.

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 both parameters are already documented, and the description largely restates them. The only added meaning is that maxChars causes truncation of long pages, which the schema's 'Maximum characters' wording only partly conveys.

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 the indexed Markdown content for a documentation URL') plus the returned format, which is concrete. It links to search_docs as the URL source but never contrasts itself with the sibling get_api, so an agent must infer that distinction.

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?

'Use a URL returned by search_docs' gives an explicit workflow dependency, telling the agent this is a follow-up fetch rather than a starting point. It does not say when to prefer get_api or what to do when a URL is not indexed, so no exclusions are stated.

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