Skip to main content
Glama

Bluebird Technologies

List pages

list_pages
Read-onlyIdempotent

Every public page with its summary, optionally of one kind: home, work, projects, about, jobs, partners, contact, checklist, quote-calculator, legal, service, case-study, newsletter. Case studies are kind "case-study"; the engagement types are kind "service".

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": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "home",
      -  "work",
      -  "projects",
      -  "about",
      -  "jobs",
      -  "partners",
      -  "contact",
      -  "checklist",
      -  "quote-calculator",
      -  "legal",
      -  "service",
      -  "case-study"
      -]New value: +[
      +  "home",
      +  "work",
      +  "projects",
      +  "about",
      +  "jobs",
      +  "partners",
      +  "contact",
      +  "checklist",
      +  "quote-calculator",
      +  "legal",
      +  "service",
      +  "case-study",
      +  "newsletter"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "home",
      -  "work",
      -  "projects",
      -  "about",
      -  "jobs",
      -  "partners",
      -  "contact",
      -  "checklist",
      -  "quote-calculator",
      -  "legal",
      -  "service",
      -  "case-study",
      -  "newsletter"
      -]New value: +[
      +  "home",
      +  "work",
      +  "projects",
      +  "about",
      +  "jobs",
      +  "partners",
      +  "contact",
      +  "checklist",
      +  "quote-calculator",
      +  "legal",
      +  "service",
      +  "case-study"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "home",
      -  "work",
      -  "projects",
      -  "about",
      -  "jobs",
      -  "partners",
      -  "contact",
      -  "checklist",
      -  "quote-calculator",
      -  "legal",
      -  "service",
      -  "case-study"
      -]New value: +[
      +  "home",
      +  "work",
      +  "projects",
      +  "about",
      +  "jobs",
      +  "partners",
      +  "contact",
      +  "checklist",
      +  "quote-calculator",
      +  "legal",
      +  "service",
      +  "case-study",
      +  "newsletter"
      +]
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely new behavioral fact: only public pages are returned, implying drafts or private pages are excluded. It says nothing about ordering, pagination, or result volume for what could be a large page set.

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 short sentences, scope stated first, then the filtering clarification and the two non-obvious enum mappings. No filler and nothing buried at the end.

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-optional-parameter read tool with full annotation coverage and no output schema, the description covers scope, return content at a high level, and filtering. The only real gap is result ordering or pagination behavior, which is minor given the tool's simplicity.

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 0%, so the description has to carry the meaning, and it does explain that the parameter is optional and what omitting it yields. It also disambiguates the two least obvious enum values: case studies map to kind "case-study" and engagement types to kind "service". The remaining eleven values are self-explanatory labels drawn from the enum itself.

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 specific verb and resource (list every public page with its summary) plus the filtering scope, so an agent knows exactly what it returns. Sibling differentiation is not explicit, but none of the listed siblings (fetch, get_contact, search) is described as a page lister, so the ambiguity is limited.

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?

The phrase "optionally of one kind" implies both the no-argument listing mode and the filtered mode, which is useful guidance. However, it never says when to prefer this over a sibling such as search, nor any exclusion, so usage is implied rather than stated.

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