Skip to main content
Glama

SPS practice prompt

sps_practice_prompt
Read-only

One TJ Student Portrait Sheet (SPS) practice prompt from the EduAvenues prompt bank, optionally for a Portrait of a Graduate skill (Communicator, Collaborator, Creative and Critical Thinker, Goal-Directed and Resilient Individual, Global and Ethical Citizen). For TJ Prep students, with the rubric lessons that apply to it.

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

Input Schema

NameRequiredDescriptionDefault
skillNoOptional Portrait of a Graduate skill

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description usefully adds that rubric lessons come bundled with the prompt, but it does not explain the idempotentHint=false signal for a read-only tool — i.e. whether the prompt is randomly selected on each call and whether the skill filter narrows or ranks the pool. That is the one behavioral trait an agent most needs here.

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?

One sentence, front-loaded with the resource being fetched, with the parenthetical skill list placed where it reads as a value set rather than an aside. The trailing fragment 'For TJ Prep students, with the rubric lessons that apply to it' is slightly choppy and could be folded in, but nothing is wasted.

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

Completeness3/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 convey the return shape; it does name two components (the prompt and the applicable rubric lessons), which is helpful. However, for a tool whose idempotency flag is false, it stays silent on selection/randomness and on how many rubric lessons or what fields accompany them, leaving a meaningful gap.

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 there is a single optional parameter, so the baseline would be 3. The description earns a bump by enumerating the exact five Portrait of a Graduate skills (Communicator, Collaborator, Creative and Critical Thinker, Goal-Directed and Resilient Individual, Global and Ethical Citizen), which the schema only calls 'Optional Portrait of a Graduate skill' — that is real, actionable value for constructing a valid call.

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 names a specific resource (one TJ Student Portrait Sheet practice prompt from the EduAvenues prompt bank) and scopes it to TJ Prep students, which is far more specific than the title alone. The retrieval verb is only implicit ('One ... prompt'), and it never explicitly says 'returns' or 'fetches', but the resource and audience make the intent unambiguous.

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

Usage Guidelines3/5

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

It supplies a usage context ('For TJ Prep students') and implies practice use of SPS prompts, but gives no explicit when-to-use versus list_lessons, get_lesson, or what_to_study, all of which are plausible siblings for practice material. No exclusions or prerequisites are stated, so the agent must infer selection.

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