Skip to main content
Glama

get_page

Read-onlyIdempotent

Use this tool when you know an Aguasto page path and need its published description, last modified date, canonical URL and Markdown link when available.

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": {
      "path": "<path>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExact published path, such as /gpus or /company.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
@typeYes
@contextYes
encodingNo
descriptionYes
dateModifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "@context": {
      +      "const": "https://schema.org",
      +      "type": "string"
      +    },
      +    "@type": {
      +      "type": "string"
      +    },
      +    "dateModified": {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "encoding": {
      +      "properties": {
      +        "@type": {
      +          "const": "MediaObject",
      +          "type": "string"
      +        },
      +        "contentUrl": {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        "encodingFormat": {
      +          "const": "text/markdown",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "@type",
      +        "encodingFormat",
      +        "contentUrl"
      +      ],
      +      "type": "object"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "format": "uri",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "@context",
      +    "@type",
      +    "name",
      +    "description",
      +    "url",
      +    "dateModified"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds a useful conditional nuance ('when available') for optional fields like the Markdown link, but since an output schema exists, the field enumeration largely repeats structured data.

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 front-loaded sentence that opens with the usage trigger and then lists return fields, with no filler. It is slightly run-on in its enumeration but every clause carries information.

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-only lookup with rich annotations and an output schema, the description covers the trigger condition and the value of the result. Details of the returned payload can be safely delegated to the output schema.

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 the path parameter is already documented with examples such as /gpus and /company. The description only reinforces that the path is a page path rather than a URL, adding marginal meaning beyond the schema.

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 gives a concrete verb-resource pair ('get ... page path') and enumerates the specific fields returned (published description, last modified date, canonical URL, Markdown link). It is clearly distinct from GPU-detail siblings, though it doesn't name them 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?

'Use this tool when you know an Aguasto page path' establishes a clear precondition that implicitly contrasts with a search-based lookup, and the schema reinforces it by requiring an 'exact published path'. It stops short of naming the alternative (e.g. search_pages) or stating when not to use it.

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