Skip to main content
Glama

InProcess Cockpit

Créateurs de l'organisation

equipe_organisation
Read-only

Les personnes de l'organisation qui construisent les cockpits avec la personne (propriétaires, créateurs), et les invitations en attente.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "equipe_organisation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read. The description adds the substantive detail that the payload includes both active owners/creators and pending invitations, which is useful behavioral context beyond the annotation. It says nothing about permissions required, whether the caller must be an owner, or whether pending invitations include emails, so the addition is modest.

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?

A single sentence with no wasted clauses, and the key scope word ('de l'organisation') comes first. The trailing phrase about pending invitations could stand alone as a second clause for faster scanning, but the sentence is efficient overall.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does name the two data groups (creators/owners, pending invitations). It does not state the shape of those records (names, emails, roles) or whether results are scoped to the caller's organization only, leaving meaningful gaps for a roster tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that could mislead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as the organization's owners/creators plus pending invitations, with the parenthetical '(propriétaires, créateurs)' clarifying scope. However, it is a noun phrase with no action verb and no explicit differentiation from closely related siblings such as equipe_cockpit or demandes_equipe, so the agent must infer that this is the org-level roster read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this tool versus alternatives; the agent is not told whether to use it for org-wide membership rather than cockpit-level teams or team requests. The closest thing to guidance is the implicit scoping in 'de l'organisation', which is not an instruction.

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