Skip to main content
Glama
Sign In

Noticiel

by io.github.waddou
OverviewDiscussionsAdmin

get_notice

Récupère le contenu complet d'une notice Noticiel (texte + lien PDF) à partir de son URL ou de son slug. Source : Noticiel.

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": {
      "url_ou_slug": "<url_ou_slug>"
    },
    "name": "get_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_ou_slugYesURL Noticiel ou slug de la fiche

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states it retrieves full content (text + PDF link), implying a read-only operation, but does not disclose authentication needs, rate limits, or error behavior. The transparency is adequate but not thorough.

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?

The description is a single, concise sentence that immediately communicates the core function. No unnecessary words, and the structure is front-loaded with the verb and key details.

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?

Given the tool's simplicity (1 required parameter, no output schema, no annotations), the description is mostly complete: it specifies input and output ('texte + lien PDF'). However, it lacks details on error handling or edge cases (e.g., invalid slug).

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% (one parameter fully described). The description does not add meaning beyond what the schema already provides (it just rephrases the input as 'URL ou slug'). Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Récupère') and clearly identifies the resource ('notice Noticiel') and input method ('URL ou slug'), making the purpose unmistakable. It distinguishes itself from siblings like 'find_pdf' by specifying full content retrieval.

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 description mentions the source ('Noticiel') but provides no explicit guidance on when to use this tool versus alternatives like 'search_notices' or 'find_pdf'. It does not explain prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Noticiel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources