find_pdf
Trouve le lien de téléchargement du PDF d'une notice sur Noticiel pour une marque et un modèle donnés. Source : Noticiel.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| marque | Yes | ||
| modele | Yes |
Noticiel
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states it finds a download link, with no mention of side effects, rate limits, authentication needs, or what happens if the PDF is not found.
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?
Single sentence with source attribution. No wasted words, appropriately sized for the tool's simplicity.
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 simple tool with 2 parameters and no output schema, the description covers basic purpose and source. However, it lacks details on failure behavior, response format, or error handling, leaving some gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It mentions marque and modele but does not add meaning beyond their names—no format, examples, or allowed values. This is insufficient for an agent to know how to provide valid inputs.
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 clearly states the tool finds a PDF download link for a manual given a brand and model. It distinguishes from sibling tools like list_marques and search_notices by specifying the exact action and source.
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 implies use when you have a specific brand and model, but provides no explicit guidance on when not to use it or alternatives among siblings. Usage is implied rather than explicit.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: find_pdf obtains a download link, get_notice retrieves full notice content, list_categories lists product types, list_marques lists brands, and search_notices performs keyword-based search. No two tools overlap in functionality.
Naming Consistency5/5
All tools consistently use snake_case with a verb_noun pattern (e.g., find_pdf, list_categories, search_notices). The naming is predictable and uniform across the set.
Tool Count5/5
With 5 tools, the server is well-scoped for its domain of accessing product manuals. Each tool covers an essential operation, and the count is within the ideal range for a focused service.
Completeness5/5
The tool set covers the full discovery-to-retrieval workflow: listing categories and brands, searching for notices, retrieving full notice content, and downloading PDFs. No obvious gaps exist for a read-only manual lookup service.