Skip to main content
Glama

get_space

Read-onlyIdempotent

Retrieve a specific Huly space by its ID or exact name. Narrow results using class or type when names are ambiguous.

Instructions

Get one generic Huly space by raw space _id or exact space name. Resolution tries _id first, then exact name. If a name matches multiple spaces, pass class and/or type to narrow; ambiguous errors include matching ids/classes/types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYesa string that will be trimmed
includeArchivedNoAllow matching archived spaces by exact name. Defaults to false for name lookup. ID lookup can return archived spaces.
classNoa string that will be trimmed
typeNoa string that will be trimmed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

The description adds value beyond annotations by detailing resolution order (_id first, then name), handling of ambiguous names, and includeArchived behavior. Annotations already indicate read-only, idempotent, non-destructive nature.

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 three sentences, front-loaded with purpose, and every sentence adds essential information without redundancy.

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?

Given the presence of an output schema and 100% parameter coverage, the description thoroughly explains the resolution algorithm and disambiguation. It covers all relevant behaviors for a simple getter tool.

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?

With 100% schema coverage, baseline is 3. The description adds significant meaning: explains how 'space' is used, the role of 'class' and 'type' for narrowing, and the distinct behavior of 'includeArchived' for ID vs name lookup.

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 specifies the verb 'Get', the resource 'generic Huly space', and the lookup methods (by _id or exact name). It clearly distinguishes from sibling tools like get_workspace_info or get_teamspace.

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?

The description explains when to use class/type parameters for disambiguation and how includeArchived behaves differently for ID vs name lookups. It doesn't explicitly state when not to use the tool, but provides clear context on resolution order.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server