Skip to main content
Glama

Add a text item

add_item

Adds the student's writing (with its attestation and the school's prompt key) or any other item as text.

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": {
      "school": "<school>",
      "application_id": "<application_id>",
      "application_token": "<application_token>",
      "item": "<item>"
    },
    "name": "add_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
schoolYesThe school's slug from list_schools, e.g. "vvs"
application_idYes
application_tokenYesThe application_token returned by verify_email for this school

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, non-idempotent, closed-world), so the description's remaining job is business rules. It does add real value by flagging that writing submissions carry an attestation and a school prompt key, but it says nothing about what happens on repeat calls, ordering, or whether items are editable afterward.

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?

A single sentence with the action front-loaded and no filler. The nested parenthetical makes it slightly harder to parse than it needs to be, 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?

For a non-idempotent mutation with a nested attestation object and no output schema, the description covers the item payload but omits what is returned, how failures surface, and the ordering relative to start_application/submit_application. It is minimally sufficient to call the tool but leaves meaningful gaps for an agent orchestrating the application flow.

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 50%, and the description only glosses the nested item fields (text content, attestation, prompt key), which the schema already documents via const constraints and field descriptions. The top-level school, application_id, and application_token parameters get no additional meaning from the description, so this is baseline adequate rather than additive.

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?

"Adds the student's writing ... or any other item as text" gives a clear verb (adds) and resource (an item submitted as text), and the phrase "as text" implicitly distinguishes it from the file-upload sibling add_file. It is somewhat convoluted by the long parenthetical, and it never names the alternative explicitly, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use statement, and no stated prerequisites (e.g., that an application must be started and the email verified first). The only guidance is implicit in "as text," which hints that binary content belongs in add_file, but the agent must infer that.

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.