Skip to main content
Glama

FișaEdu – fișe de lucru

Detaliile unei fișe FișaEdu

detalii_fisa
Read-onlyIdempotent

Detaliile unei fișe de lucru FișaEdu: clasa, materia, tema, instrucțiunile, câte exerciții are și ce cer ele (fără răspunsuri), imaginea și linkul. Folosește-l după cauta_fise, când utilizatorul vrea să știe ce conține o anumită fișă, sau când primești un link fisaedu.ro/fise/…. Get one FișaEdu worksheet by slug, id or fisaedu.ro link: grade, subject, topic, exercise list (questions only, no answers), preview and link.

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": {
      "worksheet": "<worksheet>"
    },
    "name": "detalii_fisa"
  }
}

Input Schema

NameRequiredDescriptionDefault
worksheetYesSlug-ul fișei (din cauta_fise), id-ul ei sau linkul https://www.fisaedu.ro/fise/<slug>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is additive — and it does add the critical trait that the exercise list returns questions only, with no answers. It does not say what happens with a malformed or unknown slug, which is the main remaining gap for a lookup tool.

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 content is front-loaded and the field enumeration is efficient, but the Romanian paragraph and the English paragraph are near-complete duplicates, so a large share of the text restates what was just said. Bilingual coverage has some value, but roughly half the wording does not earn new information.

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?

There is no output schema, so the description must carry the return shape — and it does, listing every field the agent will receive, including the explicit absence of answers. For a one-parameter read tool with full annotation coverage, nothing an agent needs in order to call and interpret it is missing.

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 coverage is 100% and the single `worksheet` parameter already documents the slug/id/link forms and where the slug comes from. The description restates the same three accepted forms, adding little beyond the schema; 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 names a specific verb and resource ("Get one FișaEdu worksheet") and then enumerates exactly what the record contains: grade, subject, topic, instructions, exercise list, preview image and link. This is far more than a restatement of the title and lets an agent distinguish it from a search or curriculum tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggers: use it after `cauta_fise`, when the user wants to know what a specific worksheet contains, or when a fisaedu.ro/fise/... link arrives unsolicited. The sequencing with the sibling is stated directly rather than inferred.

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