Skip to main content
Glama
@gravv/mcp

@gravv/mcp

Official

getGravvDocPage

Fetches the full text of a Gravv documentation page by slug when search excerpts lack worked examples, complete request/response bodies, or full flow diagrams.

Instructions

Fetch the full text of one Gravv documentation page by slug, as returned by searchGravvDocs. Use when an excerpt is not enough — for worked examples, complete request/response bodies, or a full flow diagram.

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": {
      "slug": "<slug>"
    },
    "name": "getGravvDocPage"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPage slug without the .md suffix, e.g. 'platform/wallets/create-a-wallet' or 'recipes/bank-payouts/pay-a-us-bank-account-by-ach'. The page's full docs URL also works, and so does the slug of a page that moved: the result names its new slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / slug / description
      Previous value: -"Page slug without the .md suffix, e.g. 'platform/wallets/create-a-wallet' or 'recipes/remit-funds-to-a-recipient'."New value: +"Page slug without the .md suffix, e.g. 'platform/wallets/create-a-wallet' or 'recipes/bank-payouts/pay-a-us-bank-account-by-ach'. The page's full docs URL also works, and so does the slug of a page that moved: the result names its new slug."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the output shape ('full text') and the intended granularity, but says nothing about failure modes, permission requirements, or what happens on a bad/ambiguous slug — the moved-page behavior exists only in the schema, not the description. Adequate but with clear gaps for an unannotated tool.

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, zero waste. The core action and its provenance come first, and the usage triggers follow immediately — properly front-loaded.

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 single-parameter read tool with no output schema, 'full text of one page' is a sufficient statement of what comes back. The only shortfall is that error and redirect behavior is left entirely to the schema, but nothing an agent needs to call it correctly is missing.

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 slug property already documents the accepted forms (bare slug, full URL, moved page) with examples. The description adds only 'by slug', repeating the schema rather than extending it, so the baseline 3 applies.

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 specific verb and resource — fetching the full text of a single Gravv documentation page by slug — and explicitly ties it to the sibling tool searchGravvDocs, which is the only source of such slugs. An agent can distinguish this from a search tool 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 Guidelines5/5

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

Gives an explicit when-to-use condition ('when an excerpt is not enough') plus concrete triggers (worked examples, full request/response bodies, flow diagrams). The alternative — using searchGravvDocs when an excerpt suffices — is implied by the contrast and by naming the sibling.

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