Skip to main content
Glama

mocop

get_organization

Read-only

Everything indexed for an organization: its APIs, MCP servers, agents, discovery results and description.

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": {
      "slug": "<slug>"
    },
    "name": "get_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description need not repeat it. The description usefully adds scope information — that the result is a bundle of indexed items spanning several resource types — which is real context beyond the annotations. It says nothing about behavior when the slug does not resolve, result size, or truncation/pagination, which are the remaining unknowns for a bulk-read tool.

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 front-loaded sentence with no filler; the resource scope is stated before the enumerated contents. The trailing 'and description' reads as an afterthought and slightly muddies the list, but overall it is tight.

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 one parameter, no output schema, and no nested objects, the tool is simple enough that a short description can suffice. However, because the only parameter is undocumented in both schema and description and no output schema exists, the agent must guess both the slug format and the exact shape of the returned bundle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter, slug, is documented nowhere. The description never explains that the argument is an organization slug/handle, what format it takes, or how it is obtained (browse_organizations is presumably the source, but the description does not say so). With zero schema coverage the description needed to compensate and does not.

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 the resource (an organization) and enumerates the concrete payload it returns: APIs, MCP servers, agents, discovery results, and description. That is specific enough to tell an agent this is an aggregate org-level fetch rather than a search. It stops short of distinguishing itself from the similarly named sibling get_organization_items, so the boundary is left to inference.

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 use this instead of get_organization_items, get_entity, or the search_* siblings. The description implies a broad 'get everything for one org' use case but never states prerequisites, exclusions, or alternatives.

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