Skip to main content
Glama
@gravv/mcp

@gravv/mcp

Official

searchGravvDocs

Search Gravv documentation for integration guides, recipes, and API reference before implementing an integration or troubleshooting unclear API errors. Returns ranked pages with excerpts for follow-up.

Instructions

Search the Gravv documentation — integration guides, recipes, and API reference, every page the docs site lists. Use this BEFORE implementing any Gravv integration, and whenever a call fails in a way the error does not fully explain. The guides carry the ordering, prerequisites, and corridor rules that the API tool schemas do not. Returns ranked pages with excerpts; follow up with getGravvDocPage for full text.

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": {
      "query": "<query>"
    },
    "name": "searchGravvDocs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results. Default 6.
queryYesWhat you want to know, in natural language. e.g. 'create a wallet on polygon', 'why is my transfer pending', 'idempotency key rules'.
sectionNoOptional filter: one docs section, as the section field of a result names it. The names come from the docs site's index, so there is no fixed list; an unknown name returns the sections there are.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / section / description
      Previous value: -"Optional filter. 'Get Started' and 'Recipes' hold end-to-end flows; 'Developer Platform' holds per-feature guides; 'API Reference' holds per-endpoint detail."New value: +"Optional filter: one docs section, as the section field of a result names it. The names come from the docs site's index, so there is no fixed list; an unknown name returns the sections there are."
    • removedInput schema / properties / section / enum
      Removed value: -[
      -  "Get Started",
      -  "Developer Platform",
      -  "Recipes",
      -  "API Reference",
      -  "Home"
      -]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it is clearly a read operation, states the return shape ("ranked pages with excerpts"), and explains why results matter ("the guides carry the ordering, prerequisites, and corridor rules that the API tool schemas do not"). It does not discuss rate limits, result pagination beyond the limit parameter, or whether the index updates, which keeps it short of a 5.

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?

Three sentences, front-loaded with the action and scope, then triggers, then the handoff to the sibling. Every clause earns its place and the "what the schemas do not cover" rationale justifies the tool's existence in one phrase.

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?

No output schema exists, and the description compensates by stating the return shape (ranked pages with excerpts) and the natural follow-up call for full text. For a three-parameter read-only search tool this is close to sufficient; only deeper operational details such as result-count limits or ranking behavior are absent.

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 all three parameters (query, section, limit) are already documented with examples and defaults; baseline 3 applies. The description adds nothing parameter-specific beyond the return shape, and the notable edge case (an unknown section name returns the available sections) lives in the schema, not the prose.

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 ("Search the Gravv documentation") and delimits scope ("integration guides, recipes, and API reference, every page the docs site lists"), which tells an agent exactly what corpus is covered. It is cleanly separated from the one sibling, which returns full page text rather than ranked excerpts.

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 explicit when-to-use triggers: "BEFORE implementing any Gravv integration" and "whenever a call fails in a way the error does not fully explain." It also names the alternative and the condition that selects it ("follow up with getGravvDocPage for full text"), so the routing decision between the two tools is unambiguous.

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