Skip to main content
Glama

get_workspace

Read-onlyIdempotent

Obtiene detalles de un workspace específico incluyendo configuración/settings

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally. The description adds only the note that returned details include settings/configuration; it says nothing about what happens if the workspace is not found or what permissions are required. With annotations carrying most of the burden, a 3 is appropriate.

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?

One short sentence with the resource and the notable payload front-loaded and no filler. It is efficient, though arguably too terse to be genuinely informative.

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 single read parameter, annotated read-only tool with no output schema, the definition is adequate but thin: the returned 'detalles' are never enumerated, so an agent cannot predict whether boards, members or settings are included. Nothing incorrect is present, but the coverage stops at minimum viable.

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% and the single parameter already documents the UUID-or-name flexibility and the 'omit if the token has a fixed workspace' rule, so the description adds nothing beyond it. Baseline 3 applies when the schema does all the parameter work.

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 ('Obtiene detalles') and resource ('workspace específico') plus a hint at payload ('configuración/settings'), so an agent knows it is a single-workspace detail reader rather than a list or search. It never differentiates itself from close siblings such as search_workspace, get_workspace_relations or update_workspace.

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 when-to-use guidance, no when-not-to-use guidance, and no named alternative. The agent must infer from the sibling names alone whether to call this rather than search_workspace or get_workspace_relations.

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