Skip to main content
Glama

Outil.io

Read service items

read_service_items
Read-only

Lister ou lire les données du compte connecté au projet : fichiers Drive/OneDrive (métadonnées seulement), emails Gmail/Outlook (message complet via get), réunions Zoom et rendez-vous Calendly. Respecte les permissions OAuth accordées ; aucune connexion personnelle MonAssocié n’est implicitement partagée. Poursuivre avec cursor=nextCursor si présent.

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

Input Schema

NameRequiredDescriptionDefault
idNo
appYes
queryNo
actionYes
cursorNo
folderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses OAuth-permission scoping, that no personal MonAssocié connection is implicitly shared, that Drive/OneDrive results are metadata only, and that pagination is cursor-based. It does not describe rate limits, error behavior, or the shape of list results, which keeps it below the top mark.

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 sentences, front-loaded with the resource scope and followed by permission caveats and pagination guidance; every sentence contributes. The parenthesis about metadata-only is dense but necessary, and no filler is present.

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

Completeness3/5

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

For a read-only multi-app retrieval tool with no output schema and zero schema description coverage, the description covers apps, action semantics, permissions, and pagination, but leaves the return format of 'list' and the filtering role of query/id/folderId unexplained. An agent would still need to guess at those inputs.

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%, so the description must carry the load: it explains the 'app' enum values, the list-versus-get meaning of 'action', and the use of 'cursor'. It says nothing about 'id', 'query', or 'folderId', so three of six parameters remain semantically undefined.

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 concrete verb pair (list/get) and enumerates the resources: Drive/OneDrive files (metadata only), Gmail/Outlook emails, Zoom meetings, Calendly appointments. That makes the tool's scope unambiguous, but it does not distinguish it from the similarly named sibling read_service_document or explain what 'service items' means versus a document.

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 actionable conditions: use 'get' when the full email message is needed, 'list' otherwise, and continue with cursor=nextCursor when a next cursor is returned. It stops short of stating when not to use this tool or naming an alternative sibling for cases it does not cover.

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.