Skip to main content
Glama

Outil.io

Read service document

read_service_document
Read-only

Lire le contenu texte complet d’un fichier Drive/OneDrive ; exporter Google Docs/Slides en texte ou le premier onglet Sheets en CSV. Les fichiers binaires doivent être joints à Oio. Nécessite les permissions du fournisseur ; si insuffisantes, l’utilisateur autorise la lecture dans les services 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>",
      "id": "<id>"
    },
    "name": "read_service_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
appYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuine context beyond that: provider permissions are required and, if insufficient, the user must authorize access in Oio services. It also discloses the conversion behavior (only the first Sheets tab becomes CSV), which is not derivable from structured fields.

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?

Two compact sentences with no filler, and the primary action is front-loaded ahead of the caveats about binary files and permissions. The density is high but appropriate for the amount of behavior being conveyed.

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?

With no output schema, the description usefully states what is returned (full text content, or CSV for the first Sheets tab) and conditions the call on provider permissions. The remaining gap is the lack of detail on the id parameter and failure behavior beyond the permission case.

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 0% for both parameters, so the description carries the burden; it does implicitly map the 'app' enum by naming Drive/OneDrive and frames 'id' as a file identifier. However it never explains the id's expected form or constraints, leaving real ambiguity for a 2-param schema.

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 names a specific verb and resource ('Lire le contenu texte complet d'un fichier Drive/OneDrive') and enumerates the formats handled (Docs/Slides to text, first Sheets tab to CSV). It is clear what the tool does, though it never contrasts itself with the sibling read_service_items.

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?

It implies usage scope by listing supported document types and warns that binary files must be attached to Oio, but it gives no explicit when-to-use/when-not guidance and never names an alternative tool for non-text files or item listings. The reader must infer that binary content is out of scope.

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.