Skip to main content
Glama

My coach's writing feedback

my_writing_feedback
Read-onlyIdempotent

The student's own EduAvenues writing feedback (SPS/PSE), released by their coach. With no submissionId, lists recent submissions per child with status and released scores. With a submissionId, returns the full released report: the prompt, the student's response, scores, rubric rows, the coach's inline comments, strengths and priorities, plus the matching TJ Prep rubric lessons. Only released feedback is ever returned.

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

Input Schema

NameRequiredDescriptionDefault
submissionIdNoA submissionId from the list (omit to list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower; the description still adds substantive context by disclosing the release-only visibility constraint and enumerating the returned contents (prompt, response, scores, rubric rows, inline comments, strengths, priorities, matching rubric lessons). It does not mention auth scoping (e.g. parent vs. student view) or how many submissions 'recent' covers.

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?

Three sentences, front-loaded with what the tool is, then a clean parallel 'With no submissionId / With a submissionId' structure, closing with the global constraint. Every clause carries information; nothing is restated from the title or schema.

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?

For a one-optional-parameter read tool with no output schema, the description must carry the return-value burden, and it does so in detail for both modes. Combined with annotations covering the safety profile, nothing an agent needs to call it correctly is missing.

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% and the single parameter is already documented with a UUID pattern and an 'omit to list' note, so the baseline is 3. The description earns above baseline by spelling out what each mode actually returns, which the schema does not convey, and by tying the id's provenance to the list call.

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 resource (the student's own EduAvenues writing feedback, SPS/PSE) and a specific source (released by their coach), then splits the behavior into two clearly enumerated modes. An agent can distinguish this from siblings like sps_practice_prompt or get_lesson without opening the schema.

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?

It explicitly states the selection rule between the two modes: no submissionId lists recent submissions, a submissionId returns the full report. It also gives the precondition that only released feedback is ever returned. It stops short of naming a competing sibling tool and when to prefer it, which keeps it from a 5.

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