Skip to main content
Glama

Atom XII

Atom XII FAQ

get_faq
Read-onlyIdempotent

Answers Atom XII publishes to common questions.

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds no behavioral context whatsoever: no indication of the breadth or static nature of the answer set, whether it is a fixed corpus, or what kind of content comes back.

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?

A single short sentence with no wasted verbiage, which is the right size for a parameterless lookup. It loses a point only because the sentence's structure is broken and reads ambiguously rather than front-loading a clear statement of purpose.

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

Completeness3/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, closed-world lookup with no output schema and full annotation coverage, the bar is modest and this clears it minimally. Still, an agent has no idea what topics the FAQ answers or what shape the response takes, which is essential for deciding between this tool and the topical siblings.

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 the baseline is 4; there is no parameter meaning for the description to supply. Schema coverage is reported as 100% for an empty object, so nothing is missing on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as an FAQ ('common questions') and implies a read/answer verb, so an agent can roughly place it against get_company and get_pricing. However, the sentence is grammatically garbled ('Answers Atom XII publishes to common questions') and never states what subject matter the FAQ covers, which is the one thing that distinguishes a generic Q&A tool from its topical siblings.

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 when-to-use guidance and no mention of alternatives or prerequisites. Given siblings like get_pricing, get_company and get_services, the definition should say whether FAQ is the fallback for general questions or whether specific topics belong in those tools; it says nothing.

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