Skip to main content
Glama

Atom Backends

Atom Backends services

get_services
Read-onlyIdempotent

The services Atom Backends offers, who each is for, its page, and its published price or how pricing works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world call, so the safety profile is fully covered and the description need not restate it. The description adds value by enumerating the returned content dimensions (audience, page, price/pricing model), which is real behavioral context beyond the annotations, but it says nothing about result size, ordering, or how pricing ambiguity is represented.

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 sentence that leads with the resource and enumerates returned fields without filler. The phrasing ('who each is for, its page') is slightly elliptical but costs little.

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 parameterless read-only lookup this is nearly sufficient, and annotations handle the safety story. However, with no output schema, the description is the only source for return-shape detail, and it omits structure (list vs. map), pagination, and how partial or missing pricing is represented.

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; baseline 4 applies. No parameter semantics are required or missing.

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 (Atom Backends' services) and the specific fields it exposes: target audience per service, the service page, and published price or pricing model. An agent can tell this is a catalog-listing tool and broadly distinguish it from get_company, even if the pricing overlap with get_pricing is not addressed.

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 description — a request about what Atom Backends offers, who a service suits, or what it costs points here. There is no explicit when-to-use statement and, notably, no routing against the sibling get_pricing despite the description claiming to cover pricing.

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