Skip to main content
Glama

Houski Property Data

search_api_documentation

Access API documentation pages for filter syntax, field references, and endpoint details. Does not bill per call. Pass an unknown page to get the full list of pages back.

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

Input Schema

NameRequiredDescriptionDefault
pageYesDocumentation page to read, for example "filter", "properties" or "pricing". Pass an unknown value to get the full list of pages back in the error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add non-obvious behavior: it discloses the cost profile ("Does not bill per call") and a fallback mechanism (unknown page returns the full list via the error). It does not state read-only semantics or the returned content format, but for a documentation-fetch tool the key behaviors are covered.

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?

Three short sentences, front-loaded with purpose, then cost, then the discovery escape hatch. Each sentence carries distinct information; only the cost sentence is slightly oddly placed between the two functional sentences.

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 no output schema, this is nearly complete: an agent knows what it retrieves, that it is free, and how to enumerate valid pages if it guesses wrong. Only the returned content format and error behavior for other failures are left unspecified.

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 coverage is 100% and the single `page` parameter is already fully documented, including the unknown-value trick, which the description merely echoes. The description restates the schema's examples rather than adding new meaning such as expected case sensitivity or exact page-name matching.

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 names a specific verb and resource ("Access API documentation pages") and enumerates the content available (filter syntax, field references, endpoint details). It does not differentiate itself from any sibling, though the sibling list contains only data endpoints rather than competing documentation tools, so the risk of mis-selection is low.

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 implied through the content categories (filter syntax, field references, endpoint details) and the discovery hint that an unknown page returns the full page list. There is no explicit when-to-use versus when-not statement, and no guidance on sequencing (e.g., list pages first, then read a specific one).

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