Skip to main content
Glama

Starter folder

starter_folder
Read-onlyIdempotent

The files a family's folder should hold for this school, with the question or instruction inside each. Offer to write them into the folder when it is empty or nearly so. Returns [{path, contents}].

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>"
    },
    "name": "starter_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesThe school's slug from list_schools, e.g. "vvs"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds real context beyond that: the output is an array of path/contents objects, and each item embeds "the question or instruction" rather than finished content, plus the note that the agent should offer before writing — signaling this tool prepares files rather than committing them.

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?

Three short sentences, front-loaded with what the resource is, then the usage trigger, then the return shape — no filler. The middle phrase "with the question or instruction inside each" is slightly compressed but still parses.

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

Completeness4/5

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

For a single-parameter read-only tool with no output schema, the definition covers purpose, trigger condition, and return shape, which is most of what an agent needs. Minor gaps remain: no detail on how many files typically come back or what the declared school slug affects.

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?

There is a single parameter at 100% schema description coverage, including its pattern and an example slug, so the schema fully carries semantics. The description only says "for this school" and adds no format or lookup detail beyond that; baseline 3 applies when the schema does the work.

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 identifies the resource concretely ("the files a family's folder should hold for this school") and states the return shape [{path, contents}], so an agent knows this is a template/starter-set retrieval rather than a listing of existing files. The verb is implicit rather than stated (no "get" or "list"), which keeps it from being fully unambiguous, but the resource and output distinguish it well from siblings like add_file.

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?

"Offer to write them into the folder when it is empty or nearly so" gives an explicit triggering condition, which is genuine when-to-use guidance. It does not name an alternative tool (e.g., add_file) for the write step it is handing off to, so the routing is clear in one direction only.

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.