Skip to main content
Glama
barzoj

somtoday-mcp

by barzoj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Assignments (hand-ins)

assignments
Read-onlyIdempotent

Retrieve and filter hand-in tasks with deadlines, status, attachments, and links; merge duplicates and include past-due items without digital hand-in.

Instructions

All hand-in assignments with their window, status (AANKOMEND, IN_TE_LEVEREN, IN_AFWACHTING, AKKOORD), teLaat (always a boolean: true only for an open hand-in past its deadline), description, attachments and links. status=open keeps upcoming and to-do ones, and by default hides past-due items where no digital hand-in is expected (inleveringenVerwacht 0, e.g. on paper; count in verborgenZonderInlevering); includeNoHandIn=true keeps them. Near-duplicates (same subject, topic, window and status, e.g. published to two groups) are merged by default, with the other ids in duplicaatToekenningIds; dedupe=false lists them separately. Use toekenningId with assignment_detail. Every item lists bijlagen (fileUrl, readable with download_attachment) and externeMaterialen; empty means the teacher attached nothing (lesmateriaal=true is only a flag, there is no separate material call).

Input Schema

NameRequiredDescriptionDefault
dedupeNoMerge near-duplicate assignments (same subject, topic, window, status). Default true.
statusNoDefault all.
leerlingIdNoNumeric leerling id. Required when more than one child is linked.
includeNoHandInNoWith status=open: also show past-due items without a digital hand-in (inleveringenVerwacht 0). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent, but the description adds substantial behavior: exact Dutch status meanings, teLaat is true only for an open past-deadline item, default hiding of inleveringenVerwacht 0 with count in verborgenZonderInlevering, and duplicate merging with duplicaatToekenningIds. It also clarifies that empty attachments means nothing was attached and that lesmateriaal is only a flag, not a separate material call.

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?

The description is dense but front-loaded: the resource and returned fields come first, then usage options. It is somewhat run-on and packs multiple behavioral details into a single paragraph, but each clause carries operational value.

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 no output schema and four optional parameters, the description is complete enough for correct invocation: it explains returned status values, attachment handling, duplicate merging, hidden-item counting, and the handoff to assignment_detail.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds useful meaning beyond the schema, particularly around status=open behavior, includeNoHandIn, and dedupe semantics with duplicaatToekenningIds; it does not explain leerlingId, which the schema already documents.

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 states a specific resource ('All hand-in assignments') and enumerates the returned fields (window, status, teLaat, description, attachments, links). It also distinguishes itself from assignment_detail by telling the agent to use toekenningId with that sibling.

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 behavioral choices: status=open vs default, includeNoHandIn=true to keep past-due no-digital-hand-in items, dedupe=false to list near-duplicates separately. It also names the routing condition to assignment_detail.

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

Deploy Server

Other Tools