Skip to main content
Glama

Search my Kliqo project

search_workspace
Read-onlyIdempotent

Find prompts, topics, tags, brands, actions, domains and URLs in a project by name. Use to turn a name into an id for another tool, or to check whether a site or competitor is tracked. Needs sign-in to Kliqo (read-only).

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": {
      "query": "<query>"
    },
    "name": "search_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
projectNoProject name, domain or id; leave out for the workspace's current project

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive behavior, so the description's bar is low, and it clears it by disclosing the auth requirement ('Needs sign-in to Kliqo'), which is not in the structured data. It says nothing about result caps or match behavior, leaving a minor gap.

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?

Two sentences, no filler, with the capability statement front-loaded before the usage guidance. Every clause adds information the agent could not get from the schema or annotations.

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 shape need not be described, and auth plus read-only status plus usage intent are all covered. The only missing piece is retrieval behavior (how many results, how matches are ranked/limited), which is minor for a two-parameter search tool.

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 coverage is only 50%: the 'project' parameter has a description while 'query' has none. The description partially compensates by saying search is 'by name' over enumerated entity types, which hints at match semantics, but it never clarifies matching (exact, prefix, substring) or the 2–200 length bounds.

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?

The description opens with a concrete verb ('Find') plus an explicit enumeration of searchable resource types (prompts, topics, tags, brands, actions, domains, URLs) scoped to a project, so the agent knows exactly what it searches. It is distinguishable from siblings like list_projects or get_actions, though it never names a sibling to contrast against.

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?

It gives two concrete situations: 'turn a name into an id for another tool' and 'check whether a site or competitor is tracked', which maps well to real agent workflows. There is no explicit exclusion or named alternative, so it stops short of a full routing rubric.

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