Skip to main content
Glama
Grist MCP Server
by nic01asFr

Describe Organization

describe_organization

Retrieves detailed information about a specific Grist organization using its ID, enabling you to inspect organization details before managing documents or records.

Instructions

Obtient des informations détaillées sur une organisation spécifique.

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": {
      "org_id": "<org_id>"
    },
    "name": "describe_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesL'ID de l'organisation à décrire

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation à décrire"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the verb. It does not confirm the operation is non-destructive, does not state any permission or access requirements, and does not characterize what 'détaillées' includes, though the batch of sibling delete/modify organization tools makes the read-only distinction worth stating.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of any usage or behavioral content.

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?

The tool is simple (one required parameter) and an output schema exists, so return values need not be explained. Still, with no annotations and no statement of access requirements or read-only nature, the definition is thinner than an agent needs when picking among the several describe_* and organization-mutating siblings.

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% and the single org_id parameter is already documented as the organization ID, so the schema does the work. The description adds only that the target is a 'specific' organization, which does not clarify the accepted integer-or-string forms beyond the anyOf in the 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?

States a specific verb ('Obtient des informations détaillées') and a specific resource ('une organisation spécifique'), so the read-only intent is unambiguous. It does not differentiate from sibling describe tools such as describe_workspace or describe_document, leaving the agent to infer the resource boundary.

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 guidance on when to choose this over describe_workspace, list_organization_access, or the modify/delete organization siblings. The usage is only implied by the tool name and the word 'détaillées', with no exclusions or prerequisites stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.