Skip to main content
Glama

Add Studocu Document Sources

add-document-sources
Idempotent

Attach up to 10 Studocu documents from search-documents to a project as project sources. Returns the added sources with their studocu:// ids; compare with document_ids if some are missing.

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": {
      "project_id": "<project_id>",
      "document_ids": "<document_ids>"
    },
    "name": "add-document-sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesUUID of the project that should receive the Studocu documents. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context.
document_idsYes1 to 10 different positive integer Studocu document ids from search-documents (documents[].id). Example: [17, 42].

Output Schema

NameRequiredDescriptionDefault
sourcesYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / sources / items / properties / url
      Added value: +{
      +  "description": "Studocu web link that opens this source in its project. Share it with the user.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / document_ids / description
      Previous value: -"One to ten unique Studocu document IDs returned by search-documents."New value: +"1 to 10 different positive integer Studocu document ids from search-documents (documents[].id). Example: [17, 42]."
    • changedInput schema / properties / project_id / description
      Previous value: -"UUID of the Studocu project that will receive the document sources."New value: +"UUID of the project that should receive the Studocu documents. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, destructive=false), so the description's real contribution is the partial-success disclosure: not all requested ids are guaranteed to be attached, and the caller should diff the returned studocu:// ids against document_ids. That is meaningful behavior an agent cannot infer from the annotations. It does not cover auth requirements or what happens to duplicates/already-attached documents beyond the idempotent hint.

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 sentences with zero filler. The action and limit are front-loaded, and the second sentence carries the return/verification information rather than burying it.

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?

An output schema exists, so return values need not be explained, yet the description still tells the agent to diff returned ids against the input — a useful completeness touch for a batch write. Remaining gaps are error/edge behavior (invalid project id, duplicates, rate limits), which are minor given the annotation and schema coverage.

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%: project_id already documents its UUID format, example, and provenance (create-project or get-context), and document_ids already states the 1–10 positive-integer range and its search-documents origin. The description only restates the 10-item cap and the id source, adding essentially no meaning beyond the schema, so the baseline of 3 applies.

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 ("Attach"), resource ("Studocu documents"), target ("a project as project sources"), and a hard limit ("up to 10"). The reference to search-documents makes it unmistakable which sibling produces the inputs, so an agent can separate this write tool from the read tool without inspecting schemas.

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?

The description routes the agent to search-documents as the upstream source of document ids and implies a post-call verification step ("compare with document_ids if some are missing"). It gives clear usage context but never states exclusions or preconditions (e.g., project must exist, already-attached documents are skipped), so it stops short of explicit when-not guidance.

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