Skip to main content
Glama

Outil.io

Get page schema

get_page_schema
Read-only

Schéma JSON complet des pages (bloc, section, style, custom, animations, survols, largeurs des deux formats). Le résumé est déjà dans les instructions du serveur : à n'appeler que pour un détail.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful redundancy context — that a summary exists elsewhere and this is the heavy detail call — but says nothing about the size/shape of the payload an agent will receive, which matters for a tool that returns a complete 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 sentences: purpose first with an enumerated scope, then the usage caveat. The parenthetical list is dense but each item earns its place by telling the agent what the schema covers. The description is written in French while the tool name, title and annotations are English, a minor inconsistency for an otherwise tight definition.

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 and no parameters, the description carries the burden of describing what comes back, and the enumerated sections (bloc, section, style, custom, animations, survols, largeurs) do that adequately. An agent knows enough to decide whether to call it, though it cannot anticipate the payload's size or nesting.

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?

There are zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter discussion.

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 names a specific resource (the complete JSON schema of pages) and enumerates what it covers (block, section, style, custom, animations, hovers, widths for both formats), so an agent knows this is the exhaustive schema dump rather than a summary. It is clear but does not explicitly contrast with the many get_page_* siblings that return actual page data, leaving some ambiguity about whether this returns data or a schema definition.

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?

It gives an explicit conditional: the summary already lives in the server instructions, so call this only when a specific detail is needed. That is genuine when-to-use/when-not-to-use guidance. It stops short of naming which sibling to call instead for the summary case, so it is not a full 5.

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.