Skip to main content
Glama

get_organization_profile

Read-only

A gym's public-facing profile and settings: description, contact, city, public page slug/visibility, branding, community switch, AI guidelines and payout mode. Use list_my_organizations for the id.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "get_organization_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety and network footprint are covered. The description adds value by disclosing the data surface (including sensitive settings like payout mode and AI guidelines), but says nothing about authorization requirements, whether hidden fields are omitted for non-admins, or error behavior for an invalid id.

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?

Two sentences, front-loaded with the resource and its returned fields, then the id-sourcing hint. The field enumeration is long but each item informs the agent about available data, so little is wasted; a slightly tighter phrasing would earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description usefully substitutes for a return-value spec by listing the exposed fields, and it resolves the required id. Missing only access/permission context and any note on partial visibility of the listed settings.

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?

Schema description coverage is 0%, so the description must carry the parameter. It does so meaningfully by telling the agent to source organizationId from list_my_organizations, which is non-obvious from the bare string schema. It stops short of stating the id format or whether slug values are accepted.

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 a specific resource ('a gym's public-facing profile and settings') and enumerates the contents (description, contact, city, page slug/visibility, branding, community switch, AI guidelines, payout mode), so an agent knows exactly what comes back. It does not explicitly contrast with update_organization_profile or get_organization_access, so sibling differentiation is only 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?

There is one concrete, actionable usage instruction: 'Use list_my_organizations for the id,' which resolves the prerequisite for the required parameter. However, there is no guidance on when to choose this over nearby reads such as get_my_profile, get_client_profile, or get_organization_access, and no stated access conditions.

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.