Skip to main content
Glama

FișaEdu – fișe de lucru

Caută fișe de lucru FișaEdu

cauta_fise
Read-onlyIdempotent

Caută fișe de lucru gata de printat pe FișaEdu (fisaedu.ro), aliniate la programa școlară din România: grădiniță (grupa mică, mijlocie, mare), clasa pregătitoare și clasele I–XII. Folosește-l când cineva cere o fișă de lucru, exerciții de printat sau o temă pentru o clasă/materie (ex. „fișă de lucru clasa a 2-a adunări până la 100”, „fișe anotimpuri grupa mare”). Returnează până la 10 fișe publicate: titlu, clasă, materie, descriere scurtă, imagine de previzualizare și linkul fișei pe fisaedu.ro. Search FișaEdu for free printable Romanian worksheets by topic, grade and subject; use it for any request for Romanian school/kindergarten worksheets. Returns up to 10 published worksheets with preview image and link; each worksheet opens, prints and downloads at its fisaedu.ro link.

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

Input Schema

NameRequiredDescriptionDefault
gradeNoGrupa sau clasa / grade: "grupa mică", "grupa mijlocie", "grupa mare", "pregătitoare", "clasa a 2-a", "2", "a V-a"… Numeric: -3 grupa mică, -2 grupa mijlocie, -1 grupa mare, 0 clasa pregătitoare, 1–12 clasele I–XII.
limitNoCâte fișe (1–10, implicit 10).
queryNoCe cauți, în română, liber: tema, noțiunea, tipul de exercițiu (ex. "adunare până la 100", "anotimpuri", "litera M"). Poate conține și clasa/materia.
subjectNoMateria / subject, în română sau engleză: "matematică", "limba română", "engleză", "științe", "math"…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the result shape ('până la 10 fișe publicate: titlu, clasă, materie, descriere scurtă, imagine de previzualizare și linkul fișei'), which matters because no output schema exists, and by noting the worksheets open/print/download at their link. It stops short of stating relevance ordering or behavior when nothing matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Romanian text is well front-loaded: purpose, then usage, then return contents. However, the entire block is then restated in English with no new information, duplicating the purpose, the usage cue and the return format. Roughly half the description is redundant, which dilutes the signal an agent should weight most.

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

Completeness4/5

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

With four fully documented optional parameters and no output schema, the description carries the return-value burden and does so adequately by naming the fields returned and the cap of 10. Coverage of what a caller needs to invoke and interpret the tool is solid. Minor gaps remain around result ordering, empty-result behavior, and when to hand off to detalii_fisa for a single worksheet.

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% — grade, subject, query and limit all carry their own documentation, including the negative-number grade encoding and the 1–10 limit default. The description adds only illustrative query strings ('fișă de lucru clasa a 2-a adunări până la 100', 'fișe anotimpuri grupa mare') that show how topic and grade can be combined in free text. That is a small increment over the schema, so the 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?

The description opens with a specific verb and resource: 'Caută fișe de lucru gata de printat pe FișaEdu (fisaedu.ro)', plus the scope of coverage (grădiniță through clasele I–XII). An agent knows immediately this is a search over a Romanian worksheet catalog. It does not, however, contrast itself with the sibling tools programa or detalii_fisa, so the differentiation is implied by 'search/returns a list' rather than stated.

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?

There is explicit when-to-use guidance: 'Folosește-l când cineva cere o fișă de lucru, exerciții de printat sau o temă pentru o clasă/materie', reinforced by two concrete natural-language request examples. What is missing is the negative case — it never says when to prefer programa or detalii_fisa instead, so the agent must infer that this is the entry-point search tool.

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