Skip to main content
Glama

FAQ

get_faq
Read-onlyIdempotent

Published FAQ answers (agents, businesses and drivers), optionally filtered by a topic such as "payment" or "proof of delivery".

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
topicNo

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely new behavioral fact — that only *published* answers are returned, i.e. drafts are excluded — but says nothing about result volume, ordering, or behavior when the topic matches nothing.

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?

One sentence, front-loaded with the resource and followed immediately by the optional filter, with zero filler. The only cost is that it is a noun phrase without a leading verb, which makes it read slightly like a label than an instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple, non-destructive, single-optional-parameter read tool with rich annotations and no output schema, so the definition need not explain return values. The description covers what it returns, who it is for, and how to narrow it — everything an agent needs to invoke it correctly.

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 description coverage is 0%, so the description must carry the parameter's meaning, and it does partially: it supplies concrete example values ("payment", "proof of delivery") that let the agent pick sensible inputs. It does not specify matching semantics — exact vs. substring, case sensitivity, or what happens on no match — which leaves a real gap for a free-text filter.

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 the resource precisely — published FAQ answers — and scopes the content to three audiences (agents, businesses, drivers), which makes it distinguishable from data-oriented siblings like list_docs_sections or get_pricing. It lacks an explicit verb ("Retrieve"/"List"), but the resource-first phrasing is unambiguous about what comes back.

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 by the word "optionally filtered by a topic," which tells the agent the call works with or without a parameter. There is no statement of when to prefer this over a sibling (e.g. list_docs_sections for documentation) and no exclusions, so the agent must infer routing.

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.