Skip to main content
Glama

Wrenform Quick Forms

Read a docs page

get_docs
Read-onlyIdempotent

Get a Wrenform docs page as Markdown (e.g. 'quick-start', 'spam', 'redirects', 'fields', 'webhooks', 'errors', 'frameworks/nextjs').

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": {
      "page": "<page>"
    },
    "name": "get_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page, e.g. 'webhooks' or 'frameworks/nextjs'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed world, so safety is covered. The description's real contribution is the Markdown return format, useful given there is no output schema, but it says nothing about behavior for an invalid page name or how to discover the full page list.

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 front-loaded sentence with the verb, resource, format and examples. Nothing is wasted and no information is withheld until later.

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 one-parameter read tool with full annotation coverage and no output schema, the definition covers what the agent needs to form a call. The only material gap is that it gives no way to enumerate available pages, leaving the agent dependent on the examples.

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?

Schema coverage is 100% and already documents the single 'page' parameter, so the baseline would be 3; however the description adds a much broader example set including hierarchical paths like 'frameworks/nextjs', which conveys that slashed nested page identifiers are valid input.

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 ('Get') and resource ('a Wrenform docs page') plus the return format (Markdown), which is enough to distinguish it from get_snippet and the quick_form tools without opening any schema.

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

Usage Guidelines3/5

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

Usage is only implied: read the docs by naming a page. It never says when to prefer this over a sibling such as get_snippet, nor what to do if the page name is unknown. The example page names do help the agent understand what content is reachable.

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