Skip to main content
Glama

Get a page

get_page
Read-onlyIdempotent

Get any other Amino Desk page as Markdown, such as costs, providers, stacks, compare/semaglutide-vs-tirzepatide or guides/protein-on-glp-1. Use search to find the path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPage path without the leading slash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the return format (Markdown) and the prerequisite that a valid path must first be resolved, which is real context beyond the structured fields given there is no output schema.

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?

Two sentences, front-loaded with the action and format, followed by examples and the fallback to search. Every clause carries information; nothing is padded.

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 one-parameter read tool with no output schema, the definition covers what it returns (Markdown), how to obtain the path, and what paths look like. It is slightly thin on failure behavior (invalid or missing page) but nothing essential to invoking it 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?

Schema coverage is 100%, so the baseline would be 3, but the description earns more by showing real slug values including multi-segment paths with slashes (compare/semaglutide-vs-tirzepatide, guides/protein-on-glp-1). That conveys the path grammar the schema's "without the leading slash" note doesn't fully illustrate.

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

Purpose5/5

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

"Get any other Amino Desk page as Markdown" names a specific verb, resource, and return format, and the word "other" scopes it away from the compound-specific siblings. The concrete path examples (costs, providers, compare/semaglutide-vs-tirzepatide, guides/protein-on-glp-1) make the resource unambiguous.

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?

"Use search to find the path" explicitly routes the agent to the search sibling when the slug is unknown, which is the main decision point for this tool. It doesn't state when-not to use it (e.g., for compound data, which get_compound covers), but the "any other page" phrasing implies that 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