Skip to main content
Glama

Get Studio entity

get_studio_entity
Read-onlyIdempotent

Fetch a single Studio catalogue entity by type and ID, with an optional workspace. Returns the JSON item or the allowed type list; use the matching list tool to find IDs.

Instructions

Fetch one Studio entity by catalogue type and id. Use the matching list_* tool to discover ids. Plural keys are canonical. Singular aliases are accepted. Read-only. Returns JSON item or the allowed type list.

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": {
      "entity": "<entity>",
      "entity_id": "<entity_id>"
    },
    "name": "get_studio_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesCatalogue key such as personas, crews or knowledge_stacks. Singular aliases such as persona are accepted.
entity_idYesRow id in that table.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed2 schema fields changedv6.2.1
    • addedInput schema / properties / entity / description
      Added value: +"Catalogue key such as personas, crews or knowledge_stacks. Singular aliases such as persona are accepted."
    • addedInput schema / properties / entity_id / description
      Added value: +"Row id in that table."
  3. Addedv6.1.5

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world access, so the safety profile is covered; the description's 'Read-only' is largely redundant. It does add real behavior beyond the schema: invalid type input returns the allowed type list rather than failing opaquely, and the canonical-vs-alias key handling is spelled out.

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?

Five very short sentences, front-loaded with purpose before alternatives and key conventions. Minor waste in repeating 'Read-only' (already in annotations) and splitting the alias rule into two sentences.

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?

An output schema exists, so return-value documentation is not strictly needed, yet the description still signals the two possible responses (item vs. allowed type list). Combined with full schema coverage and read-only/idempotent annotations, an agent has enough to call it correctly; only named-sibling routing is left implicit.

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%, so all three parameters are already documented in the schema, including the singular-alias rule for `entity` and the workspace defaulting behavior. The description's 'Plural keys are canonical. Singular aliases are accepted' restates the schema rather than adding syntax or format detail, so the baseline 3 applies.

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 concrete verb and resource ('Fetch one Studio entity') plus the two keys that identify it (catalogue type and id), which clearly separates it from bulk/list operations. It stops short of 5 because the alternative it points at is a generic 'matching list_* tool' rather than a named sibling.

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

Usage Guidelines4/5

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

Gives usable guidance: call this to fetch a single entity, and use the matching list_* tool first to discover ids. That establishes the lookup-then-fetch workflow, though there are no explicit exclusions (e.g., when to prefer list_studio_catalogue directly) or stated preconditions.

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