Skip to main content
Glama

Studocu Project State

get-project-state
Read-onlyIdempotent

List the project sources and creations inside one or more projects. A creation may include external_id (a quiz id or mock-exam id) to match a request-creation result that is still being saved.

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": {
      "ids": "<ids>"
    },
    "name": "get-project-state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes1 to 20 project ids from get-context or create-project. Example: ["11111111-1111-4111-8111-111111111111"]. Projects you cannot access are left out.

Output Schema

NameRequiredDescriptionDefault
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / projects / items / properties / creations / items / properties / url
      Added value: +{
      +  "description": "Studocu web link that opens this item in its project. Share it with the user.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / projects / items / properties / sources / items / properties / url
      Added value: +{
      +  "description": "Studocu web link that opens this item in its project. Share it with the user.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / projects / items / properties / url
      Added value: +{
      +  "description": "Studocu web link to the project. Share it with the user.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / ids / description
      Previous value: -"The project ids to load sources and creations (project state) for. Only projects you can access are returned."New value: +"1 to 20 project ids from get-context or create-project. Example: [\"11111111-1111-4111-8111-111111111111\"]. Projects you cannot access are left out."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. Beyond that, the description discloses genuinely non-obvious behavior: a creation may carry external_id (a quiz id or mock-exam id) used to correlate against a pending request-creation result, which is semantics the schema and output schema alone would not convey.

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?

Two tight sentences with no waste. The primary purpose is front-loaded and the second sentence adds only the one non-obvious detail about external_id.

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 a full output schema and complete annotations, the description covers purpose and the one subtle output behavior. The only gap is sibling routing - it does not tell the agent when to prefer this over get-context or request-creation - which is minor given the clarity of the stated purpose.

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 100% and the single ids parameter is fully documented in the schema, including the 1-20 bound, an example, and the note that inaccessible projects are omitted. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource - list the project sources and creations inside one or more projects - so an agent knows exactly what it retrieves. It is distinct from siblings such as get-context or create-project by virtue of the resource named, though it never explicitly contrasts itself with them, keeping it just 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 Guidelines3/5

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

There is no explicit statement of when to choose this over get-context or other siblings. The second sentence hints at a usage context - matching a request-creation result that is still being saved - which implies polling behavior, but the agent has to infer that this is the tool for checking whether an in-flight creation has landed.

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