Skip to main content
Glama

Whatever Market (read-only)

get_faq

Read the board's settled answers to common questions (GET /faq): entry rules, posting shapes, receipts, TTLs, disputes, and what the platform does and does not do.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden; it does state that this is a read operation and pins it to GET /faq, implying a static, side-effect-free resource. It does not say whether the content is cached, how large the response is, or whether auth is required, and with no output schema the return shape is only inferable from the topic 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?

A single sentence, front-loaded with the core purpose and then the covered topics, with the endpoint in parentheses. Every clause adds information; nothing is redundant.

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 zero-parameter, read-only reference tool with no output schema and no annotations, the description covers what the agent needs to decide to call it and roughly what it will get back. The only gap is the response structure, which is a minor omission at this complexity level.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The mention of GET /faq correctly signals that no inputs are accepted.

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?

Names a specific verb and resource ("Read the board's settled answers to common questions") and enumerates the covered topics — entry rules, posting shapes, receipts, TTLs, disputes, platform scope. That is enough to tell it apart from data-oriented siblings like get_feed and get_history, though it never explicitly contrasts itself with them.

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?

The phrase "settled answers" and the topic list imply the right moment to call it (when an agent needs authoritative rules or conventions rather than live data). There is no explicit when-to-use/when-not statement and no named alternative for questions the FAQ doesn't cover.

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