Skip to main content
Glama

docs-get_whitepaper

Retrieves the B2B technical whitepaper from Exeris documentation so AI agents can review architecture and integration details.

Instructions

Fetch the B2B technical whitepaper (b2b-technical-whitepaper.md) from exeris-docs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description still makes clear this is a read-only fetch of a fixed document from a named source, which is useful context. However, it says nothing about what happens if the document is absent, what the returned content looks like (raw markdown vs. structured), or its approximate scope, so the behavioral burden is only partly carried.

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?

One sentence, front-loaded with the verb and the resource, with the concrete filename embedded as clarification. Nothing is redundant and nothing could be cut without losing information.

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 trivial zero-parameter retrieval with no output schema and no annotations, the definition covers what is fetched and from where, which is enough to call it correctly. The only shortfall is a lack of any hint about return shape or what the whitepaper covers, which would help an agent judge relevance before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema declares zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description usefully pins down the single fixed target the call resolves to, which is the only semantic content a zero-arg tool can have.

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?

The description pairs a specific verb ('Fetch') with a specific, named resource ('B2B technical whitepaper (b2b-technical-whitepaper.md)') and its source collection ('exeris-docs'). Naming the exact document distinguishes it from sibling document fetchers such as docs-get_adr, docs-get_hla and docs-get_repo_doc, though it never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to choose this over the sibling document tools (docs-get_repo_doc, docs-search, docs-list_repo_docs) or on any prerequisites. The use case is only implied by the document name; no exclusions or alternatives are mentioned.

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