Skip to main content
Glama

diagnostico_inicial

Assess a new Polish learner's proficiency with level-based exercises (A1/A2/B1) to determine their appropriate starting point.

Instructions

Ejercicios repartidos por nivel (A1/A2/B1) para situar a un alumno nuevo. Úsala cuando alguien empiece o pida saber su nivel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
Behavior2/5

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

No annotations are provided, so the description must carry full responsibility for behavioral disclosure. It does not mention side effects, whether it mutates student state, return format, or any actions beyond providing exercises. The phrase 'to place a new student' implies a placement outcome but lacks explicit detail.

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?

The description is two sentences, front-loaded with the core function and immediately followed by usage guidance. Every sentence earns its place with no wasted words.

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

Completeness2/5

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

With one parameter, no output schema, and no annotations, the description is incomplete. It explains the purpose and usage but omits the meaning of 'n' and any details about the response or side effects. For a simple tool, this leaves significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter 'n' with zero description coverage in the schema and no mention in the tool description. The description completely fails to explain what 'n' represents (e.g., number of exercises, level, or something else), making it impossible for an agent to correctly supply this parameter.

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 provides exercises distributed by level (A1/A2/B1) to place a new student, which is a specific verb+resource+scope. It distinguishes itself from sibling tools by explicitly targeting new student level placement.

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?

The description explicitly says 'Use it when someone starts or asks to know their level', providing clear when-to-use guidance. It does not mention when-not-to-use or alternative tools, but the usage context is well-defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maution/polski-tutor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server