Bab Aljazair

Show an interactive consular dossier

show_consular_dossier

Read-only

Render an interactive Bab Aljazair dossier checklist for a resolved office and procedure. Use once the office and procedure IDs are known, especially when the user wants to prepare, personalize, or track the dossier.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`language`	No	Response language: Arabic, Tamazight (Kabyle), English, or French.	fr
`officeId`	Yes	Consular office identifier returned by an office tool.
`applicants`	No	Optional applicants used to tailor person-specific requirements.
`procedureId`	Yes	Procedure identifier returned by the search tool.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	Yes
`office`	Yes
`research`	Yes
`checklist`	Yes
`procedure`	Yes
`applicantCount`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already show readOnlyHint=true and destructiveHint=false. Description adds 'interactive' and 'dossier checklist' context, but does not detail interactivity scope. No contradictions.

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 sentences, front-loaded with purpose, no redundant information. Every sentence is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema and annotations, the description sufficiently covers the tool's purpose, usage context, and expected behavior for a display-only tool.

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%, so description adds no extra parameter meaning beyond what schema provides. Baseline score of 3 is appropriate.

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 'Render' and resource 'interactive dossier checklist', clearly distinguishing it from sibling tools that search or list offices/procedures.

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?

Explicitly states when to use: 'once the office and procedure IDs are known' and for 'prepare, personalize, or track'. Lacks explicit alternatives but context is clear.

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

All Bab Aljazair tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: retrieving procedure details, listing offices, locating an office by address, searching procedures, and showing a dossier. There is no overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_consular_procedure, list_consular_offices), making them predictable and easy to understand.

Tool Count5/5

5 tools is well-scoped for the domain of Algerian consular services. Each tool serves a necessary function without being overly numerous or sparse.

Completeness5/5

The tool set covers the primary user workflow: finding offices, locating the correct office, searching for procedures, retrieving detailed procedure info, and generating a dossier. There are no obvious gaps for a read-only information service.

Resources

Need Help?