Skip to main content
Glama
Sign In
zyta-sign-mcp

zyta-sign-mcp

by blanck1945
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Detalle de estudio

kairo_get_studio

Retrieve a studio with its areas, members, and your assigned role using a studio ID.

Instructions

Obtiene un estudio con áreas, miembros y tu rol.

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": {
      "studioId": "<studioId>"
    },
    "name": "kairo_get_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
studioIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the return content (areas, members, role) but does not explicitly state that the operation is read-only or idempotent, nor does it mention any side effects. For a straightforward getter, this is adequate but not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that directly states the purpose and key included data. It is front-loaded and contains no unnecessary words.

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?

For a simple get operation with one parameter and no output schema, the description provides the core information but lacks details like error conditions, prerequisites, or a full explanation of the return object. It mentions areas, members, and role, which is helpful, but could be more comprehensive.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention the 'studioId' parameter at all. The parameter lacks any description in the schema, and the tool description fails to compensate by explaining what the parameter is or how to use it. This is a significant gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves a studio with areas, members, and the user's role. It distinguishes from sibling tools like kairo_list_studios (which lists all studios) and kairo_create_studio (which creates). The verb 'obtiene' is specific to fetching a resource.

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?

The description implies that this tool is used when you need detailed information about a single studio, but it does not explicitly state when to use it versus alternatives like kairo_list_studios or when not to use it. There is no exclusion or alternative naming.

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

Deploy Server

Other Tools