Skip to main content
Glama

Outil.io

Write service document

write_service_document

Créer un fichier texte dans Drive/OneDrive ou remplacer son contenu (id fourni). Fournir name et content ; folderId facultatif pour création. Un fichier existant doit être lu avant remplacement ; version/ETag si disponible. Ne convertit pas un document Office en texte silencieusement : réservé aux fichiers texte demandés. Exige les droits d’écriture OAuth accordés par l’utilisateur dans Oio.

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": {
      "app": "<app>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "write_service_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
appYes
nameYes
contentYes
versionNo
folderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true) it discloses real behavioral traits: a read-before-replace safeguard, optimistic concurrency via version/ETag, an explicit non-behavior (no silent Office-to-text conversion), and an authorization requirement (write OAuth granted in Oio). This is exactly the kind of context the hints do not carry.

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?

Front-loaded with the create-or-replace decision, then prerequisites, then caveats — each sentence adds a distinct constraint rather than restating the name. It is dense but not padded; a slightly tighter split for readability would earn a 5.

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 mutation tool with 6 parameters, no output schema, and zero schema descriptions, the definition covers modes, prerequisites, concurrency, non-conversion scope, and permissions. What remains unstated — return value and the file being overwritten beyond the read-first rule — is minor for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it largely does: `name` and `content` for writes, `id` for replacement mode, `folderId` as optional at creation, `version` as the ETag/version guard, and Drive/OneDrive named for the `app` enum. The mapping of `version` to concurrency semantics is valuable; only the enum values themselves and size caps are left to the schema.

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?

The description names a concrete verb pair (create / replace content) on a concrete resource (text file in Drive or OneDrive), and disambiguates the two modes by the presence of an `id`. It is clearly the write counterpart to `read_service_document`, and an agent can tell write-create from write-replace from the text alone.

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?

It gives clear mode-selection guidance: supply `name` and `content` for creation, `folderId` optionally when creating, and `id` when replacing. It also states prerequisites (an existing file must be read before replacement, use version/ETag when available). It stops short of naming the sibling tool to use for that prior read, so the routing is implied rather than explicit.

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.