Skip to main content
Glama

eSignStack Docs

Search documentation

search_docs
Read-onlyIdempotent

Search the eSignStack guides and the API reference. Returns matching pages with a snippet; read one with read_doc.

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": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 8).
queryYesWords to look for, for example "webhook signature" or "void envelope".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral fact is the return shape (matching pages with a snippet), which is useful but thin; it says nothing about result ordering, empty results, or corpus freshness.

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 compact sentences with the scope front-loaded and no filler. Minor deduction because the return-shape detail and the sibling pointer are packed into one sentence, slightly blurring the structure.

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, so the description correctly carries the burden of saying what comes back (pages plus snippet), which is the key missing piece an agent needs. It's near-complete for a two-parameter read-only search, though it could say whether results are ranked or paginated.

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 query and limit are already documented including the default of 8 and the max of 20. The description adds no syntax, quoting, or query-construction guidance beyond the schema's own examples, so 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 ("Search the eSignStack guides and the API reference") and scopes the corpus to two named sources. It also distinguishes itself from its sibling by pointing at read_doc for the follow-up step.

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?

Gives clear usage context and a next-step route ("read one with read_doc"), so the search-then-read workflow is obvious. It stops short of stating exclusions, such as when to skip search and go straight to the API reference, so it's short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources