Skip to main content
Glama

Outil.io

List legal pages

list_legal_pages
Read-only

État des pages légales du site : type, page, slug, publiée ou brouillon, à relire.

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_legal_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 the safety profile is covered structurally. The description adds genuine value by disclosing what the response surfaces — a per-page publication state and a review flag — which no annotation conveys. It stops short of saying whether all pages are always returned or whether results are scoped or ordered.

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 noun phrase with a colon-delimited field list — nothing superfluous. It reads as a terse fragment rather than a complete sentence, and it is written in French while the title, siblings, and all other metadata are English, which adds a small parsing cost.

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?

For a zero-parameter read with no output schema, the description should carry the whole burden of explaining what comes back, and it only partly does. It names the fields but not scope (all legal pages or only drafts?), ordering, or whether a count is included.

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?

The tool takes zero parameters, so the schema carries nothing that the description needs to compensate for; baseline for a parameterless tool applies. The sentence clarifies the field-level payload instead, which is a reasonable substitute.

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 site's legal pages — and enumerates the state it exposes (type, page, slug, published vs. draft, to-review). That is far more than a restatement of the name, though it never contrasts itself with adjacent siblings such as list_pages, list_payment_pages, or generate_legal_pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The trailing phrase 'à relire' faintly hints at a review workflow, but an agent gets no guidance on choosing this over list_pages for a general page audit.

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.