get_service_org
Retrieve a specific service organization by providing its unique ID.
Instructions
Retrieve a specific service organization by ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| soId | Yes | The service organization ID |
Retrieve a specific service organization by providing its unique ID.
Retrieve a specific service organization by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| soId | Yes | The service organization ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds no behavioral context beyond annotations; readOnlyHint and destructiveHint already convey safety. No contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single front-loaded sentence with zero waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read operation with one parameter and no output schema, the description is complete and sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Parameter soId is fully described in schema (100% coverage); description adds no extra meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses clear verb 'Retrieve' and resource 'service organization by ID', distinguishing from list and create siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage when you have a specific ID, but lacks explicit guidance on when to use vs alternatives like list_service_orgs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/theonlytruebigmac/n-central-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server