Skip to main content
Glama

Read the Atly API guide

get_docs
Read-onlyIdempotent

Read the documentation

Returns the API guide as Markdown: what each operation is for, how to turn a user's request into category ids and a location, request and response shapes, how to read scores. Call this once per session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
guideNoThe full guide, as Markdown: the same as the text content. Absent for ChatGPT, which shows the model the text content too.
call_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / description
      Previous value: -"The guide itself is the tool result's text content (Markdown); structuredContent carries only the call_id."New value: +"The guide itself is the tool result's text content (Markdown); structuredContent carries the call_id and, except for ChatGPT, the same guide as `guide`."
    • addedOutput schema / properties / guide
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The full guide, as Markdown: the same as the text content. Absent for ChatGPT, which shows the model the text content too."
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The guide itself is the tool result's text content (Markdown); structuredContent carries only the call_id.",
      +  "properties": {
      +    "call_id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "call_id"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is to add what's missing — and it does: the return format (Markdown) and the fact that the payload is a whole guide rather than a query result. The 'once per session' advice also signals cost/latency characteristics and discourages redundant calls, which annotations do not convey.

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?

Short and front-loaded: the core action comes first, then the content inventory, then the cadence rule. The opening line 'Read the documentation' is slightly generic and the mid-sentence line break is awkward, but there is no filler.

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?

For a zero-parameter documentation tool with an output schema already describing the return, the description supplies everything an agent needs: what the guide contains, what format it arrives in, and how often to call it. Nothing essential is missing.

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. No misleading parameter language is 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?

States a concrete verb and resource: 'Returns the API guide as Markdown', and enumerates the guide's contents (operation purposes, mapping requests to category ids and location, request/response shapes, reading scores). This clearly separates it from data-fetching siblings like search_places or list_categories, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit cadence guidance — 'Call this once per session' — which is exactly the trigger an agent needs. It lacks an explicit 'when not to call' clause or a pointer to a sibling for deeper questions, so it stops short of full routing guidance.

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.