Skip to main content
Glama

Atom XII

About Atom XII

get_company
Read-onlyIdempotent

Who Atom XII is, key facts, who it serves, languages, and how to reach it (booking links, inquiry endpoints, privacy).

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_company"
  }
}

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?

Annotations already declare this a safe, idempotent, read-only, closed-world lookup, so the description's remaining burden is light. It adds one useful behavioral signal by framing booking links and inquiry endpoints as information returned rather than actions performed, but it says nothing about freshness, staleness, or the shape of the response.

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 front-loaded sentence that leads with the core purpose and then lists scope items. Every clause maps to retrievable content with no filler or repetition.

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 parameterless, read-only info tool with no output schema, the description covers enough for an agent to call it correctly and know what categories of content to expect. It only falls short on how this differs from the more specific sibling lookups.

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 schema has zero parameters, so the baseline is 4 and there is nothing parameter-level for the description to compensate for. No misleading hints about arguments are present.

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 resource and enumerates its contents: identity, key facts, audience, languages, and contact/privacy info. It is clear what an agent gets back, but it never distinguishes itself from siblings like get_faq, get_pricing, or get_services, which plausibly overlap with 'key facts'.

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 by the content enumeration – an agent can infer 'call this for general company background.' There is no explicit when-to-use framing and no routing away from get_faq or get_pricing when the question is specifically about FAQs or prices, so the agent must guess the boundary.

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