Skip to main content
Glama

Read an app page

get_app
Read-only

The full page for one app, as markdown: overview, features, requirements, downloads, one-line install, MCP setup, FAQ.

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": {
      "id": "<id>"
    },
    "name": "get_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesApp id from list_apps, e.g. "gitagent".
localeNoLanguage of the content: en or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the response is markdown and includes specific sections (overview, features, requirements, downloads, install, MCP setup, FAQ), which tells the agent what to expect from the payload.

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 compact sentence that front-loads the return format and then lists contents; every clause earns its place with no filler.

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?

With no output schema, the description usefully enumerates the returned sections and format, which is the main thing an agent needs. The only gap is locale-driven behavior and the id-discovery workflow, both of which the schema already supplies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters (id, locale) are documented in-schema, including the cross-reference to list_apps and the enum values. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Names the specific resource ('the full page for one app') and enumerates exactly what it contains, which clearly separates it from list_apps or search. The action verb is only implied ('the full page'), and sibling routing (get_post, get_learning_path) is left to inference, so it stops short of a 5.

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 implied: fetch the detail page once you have an app id. There is no explicit when-to-use/when-not statement, and the 'get the id from list_apps first' workflow appears only in the schema, not the description.

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