Skip to main content
Glama

workspace-search

Find boards and cards by title in a workspace. Use a search query and optional limit to narrow down results.

Instructions

Searches for boards and cards by title within a workspace (Tags: Workspaces)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspacePublicIdYes
queryYes
limitNo
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states it searches by title but does not disclose important aspects such as pagination, sorting, whether both boards and cards are returned together, or behavior when no results are found.

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?

The description is very short (one sentence plus tags), which is efficient. However, it could be slightly more informative while remaining concise. It earns a high score for brevity but low for richness.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description is incomplete. It does not describe what the tool returns (e.g., list of boards and cards), nor does it address potential edge cases or the structure of results. For a search tool, this is a notable gap.

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

Parameters2/5

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

The input schema has no descriptions (0% coverage). The description adds only that the search is 'by title', implying the 'query' parameter is a title search, but this is insufficient. It does not explain the format of workspacePublicId or the limit parameter beyond schema constraints.

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 what the tool does: searches for boards and cards by title within a workspace. The verb 'searches' and specific resources 'boards and cards' provide a clear purpose, and it distinguishes from other tools that focus on single board or card operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It only mentions 'Tags: Workspaces', which vaguely hints at workspace scope, but there is no explicit when or when-not to use it, nor are any alternative tools mentioned.

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/AixLabTech/kanbn-mcp'

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