Skip to main content
Glama

Wadifa Info: Morocco Public Jobs

Search past exam papers

search_exam_papers
Read-only

Search the library of past Moroccan public recruitment exam papers (sujets / نماذج مباريات), many with a correction.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeywords: grade, employer, subject or year.
langNoLanguage of the labels: fr (default) or ar.
pageNoPage number, default 1.
sizeNoResults per page, 1-100, default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds real content context ('many with a correction'), which is a useful behavioral trait, but says nothing about result ordering, pagination limits, or how corrections are surfaced.

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 dense sentence with the resource scoped front-to-back and no filler. Slightly under-informative rather than bloated.

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 search tool with four optional params and no output schema, the description omits what a result actually contains (title, year, grade, download link, presence of correction). It is adequate to invoke the tool but not to anticipate its output.

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 q, lang, page and size are all documented in the schema itself. The description adds no syntax hints (e.g. how to combine grade/employer/year keywords), so baseline 3 applies.

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?

States a specific verb (search) and a precisely scoped resource (past Moroccan public recruitment exam papers), including the multilingual terms users may actually query with. It does not, however, draw a line against sibling tools like get_exam_paper or search_concours.

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 word 'Search' and the sibling naming (get_exam_paper being the retrieve-by-id counterpart) imply when to use it, but nothing explicit is given about when to prefer this over search_concours or get_exam_paper, nor about empty-result handling.

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.

Resources