Skip to main content
Glama

search_pages

Read-onlyIdempotent

Use this tool to find published Aguasto references by topic. Returns matching titles, descriptions and canonical links to the full sourced pages.

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": {
      "query": "<query>"
    },
    "name": "search_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of ranked matches to return.
queryYesTopic or keywords to match against published titles and descriptions.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +5
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of ranked matches to return."
    • addedInput schema / properties / query / description
      Added value: +"Topic or keywords to match against published titles and descriptions."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "results": {
      +      "items": {
      +        "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"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered and the description only needs to add context. It adds that results are limited to *published* material and that matches are ranked (implied by the limit parameter), but discloses nothing about ranking behavior or result volume beyond the schema.

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?

Two short sentences, front-loaded with the purpose before the return shape, with no redundancy. The only waste is the boilerplate opener "Use this tool to".

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?

An output schema exists and annotations are rich, so the description needn't explain returns or safety. However, for an agent deciding between this and get_page, the missing hand-off guidance and the unexplained "Aguasto" domain reference leave a real gap.

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 description coverage is 100%, so both query and limit are already documented with constraints (1-2000 chars, 1-20 results). The description adds no syntax, matching behavior, or format guidance beyond "by topic", so the baseline of 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?

"Find published Aguasto references by topic" gives a specific verb (find) plus the resource (published references/pages) and the matching dimension (topic). It is clear enough to distinguish from retrieval-style siblings, though it never names get_page, which is the obvious follow-up for reading a full page.

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?

"Use this tool to find published references by topic" implies the usage context (keyword lookup), but there is no statement of when not to use it and no named alternative such as get_page for fetching full content. Guidance is present but entirely implicit beyond the opening clause.

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