Skip to main content
Glama

Add a file

add_file

Uploads one PDF, JPG, PNG, HEIC or DOCX (base64, 20 MB max) as an item.

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>",
      "meta": "<meta>",
      "filename": "<filename>",
      "base64": "<base64>"
    },
    "name": "add_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaYes
base64Yes
schoolYesThe school's slug from list_schools, e.g. "vvs"
filenameYes
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.1/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description usefully adds the accepted MIME formats and the 20 MB upload limit, which appear nowhere in the structured fields, but it is silent on what happens on rejection (bad type, oversize), that re-uploading duplicates rather than replaces, and the attestation requirement attached to 'writing' meta types.

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 dense sentence that front-loads the verb and enumerates the formats and limit without filler. It is efficiently sized, though the parenthetical packing of format and size slightly hurts scannability.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-required-parameter, nested-object mutation with no output schema and no annotations beyond basic hints, the description is too thin: it never explains how to populate meta.type, when attestation is mandatory, or what a successful upload returns. An agent would have to reverse-engineer the workflow from the raw schema.

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 only 33% across six required parameters, so the description should carry weight; it does add the accepted file formats and size cap that the schema never constrains. However it says nothing about the nested meta object, whose nine-value type enum and attestation sub-object (with const-constrained fields) are the most error-prone part of the call, nor about filename or application_id semantics.

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?

States a specific verb ('Uploads') and resource ('a file ... as an item') plus concrete accepted formats and a size ceiling, which tells an agent exactly what the call achieves. It does not, however, distinguish this from the sibling 'add_item', and the phrase 'as an item' is the only hint about the relationship between the two.

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 when-to-use guidance at all: no statement of prerequisites (e.g. that application_id and application_token come from verify_email and that the slug comes from list_schools), no condition under which to choose add_file over add_item, and no exclusions. The agent must infer the workflow entirely from the schema.

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.