Skip to main content
Glama
Sign In

Fiveable for AP Teachers

by io.github.thinkfiveable
OverviewDiscussionsAdmin

Import essays from files

import_essays_from_files

Splits teacher-supplied PDFs or Word stacks into one essay per student, including AP Classroom 'FRQ Response PDFs, By Student Page Break' exports. Photos support one essay per image and are read by Fiveable. Accepts up to three ChatGPT attached uploads of 25 MB each, or up to three base64 files totaling about 3 MB. Returns counts and warnings only. Long PDFs can take up to a minute.

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": {
      "sessionId": "<sessionId>",
      "files": "<files>",
      "uploads": "<uploads>"
    },
    "name": "import_essays_from_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
uploadsYesFiles the teacher attached in ChatGPT, passed by reference.
sessionIdYesGrading session id from list_grading_sessions or create_grading_session.

Output Schema

NameRequiredDescriptionDefault
textNoReadable tool result text for clients that consume structured output.
statusYesOperation status: completed, pending, partial, failed, unavailable, or a domain-specific outcome.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Excellent behavioral disclosure beyond annotations: it describes the splitting logic (one essay per student), supported formats (PDF, Word, photos), photo handling (one essay per image, read by Fiveable), size limits (25 MB uploads, ~3 MB base64 total, up to 3 files), return value behavior ('Returns counts and warnings only'), and a performance warning ('Long PDFs can take up to a minute'). This is rich, non-obvious context.

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 tightly packed into four sentences, each earning its place with concrete, useful details. It is front-loaded with the core splitting behavior and then flows into format support, size limits, return behavior, and performance note without waste.

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 the tool's complexity (file parsing, splitting, multiple formats, size/upload limits), the description covers all critical behavioral aspects: input types, splitting logic, size constraints, return value scope, and latency warning. The output schema exists, so return details need not be repeated. This is complete for an agent to invoke correctly.

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 description coverage is 67% – moderate. The description adds meaning by explaining that 'uploads' are 'ChatGPT attached uploads' and 'files' are teacher-supplied base64 files, but it does not clarify format expectations or constraints for individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Import essays from files') and details exactly what it does: 'Splits teacher-supplied PDFs or Word stacks into one essay per student.' It names the specific format ('AP Classroom FRQ Response PDFs, By Student Page Break exports') and distinguishes itself from siblings import_essays_from_google_classroom and import_essays_from_text by being file-based.

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?

The description implies when to use it (when you have teacher-supplied PDFs/Word stacks/photos) but does not explicitly state when to use this versus import_essays_from_text or import_essays_from_google_classroom. An agent must infer from the input schema and sibling names.

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

All Fiveable for AP Teachers toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources