Skip to main content
Glama

mocop

get_organization_items

Read-only

List the APIs, MCP servers or agents of an organization (kind: api, mcp, agents, site), or one item.

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>",
      "kind": "<kind>"
    },
    "name": "get_organization_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo
kindYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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. The description adds nothing about return shape, pagination, or what happens when a slug or item is not found — for a listing tool with no output schema, that leaves real behavioral gaps.

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 wasted words; the resource list comes first and the modifier follows. Minor internal inconsistency: 'site' appears in the kind enumeration but not in the leading list of resource types.

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?

Three undocumented parameters, no output schema, and no pagination or error semantics. The description covers the core enumeration intent but is not complete enough for an agent to confidently form calls, especially for the optional 'item' parameter.

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 coverage is 0%, so the description must carry parameter meaning. It does enumerate the kind values (api, mcp, agents, site), which is valuable, but it never explains 'slug' (organization identifier) and only gestures at 'item' with 'or one item' without saying whether it is an ID, name, or slug.

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 ('List') and the concrete resource types (APIs, MCP servers, agents) scoped to an organization, plus the single-item variant. It does not name a sibling to contrast with (e.g., search_apis), so the boundary between this org-scoped listing and the search_* tools is left implicit.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer 'use this to enumerate an org's items, or fetch one by item'. There is no explicit when-to-use/when-not or guidance on choosing this over search_apis or search_mcp_servers for the same resources.

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