Skip to main content
Glama

Search Playground nodes

playground_nodes_search
Read-onlyIdempotent

Search node IDs, types, titles, text, and prompts. Returns bounded summaries with pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return in this page.
queryYesSearch words describing the item or content to find.
offsetNoNumber of matching results to skip; use the previous response’s nextOffset for another page.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
nodesYes
totalYes
offsetYes
hasMoreYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful context with "bounded summaries" and pagination behavior, which tells the agent results are truncated and pageable. It stops short of explaining matching semantics (exact vs. semantic) or result ordering, which matter for a search tool.

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, zero filler, with the searchable fields listed first and the result-shape note second. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be spelled out, and the schema covers all four parameters fully. What remains missing is search-relevant context: what a "node" is in this product, whether matching is lexical or semantic, and how results are ranked, all of which an agent needs to interpret a query result.

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%, with each of limit, offset, query, and projectId already documented in detail, including the nextOffset paging hint. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource set: "Search node IDs, types, titles, text, and prompts." An agent knows exactly what corpus is being searched. However, it does not differentiate itself from plausible siblings such as playground_memory_search or playground_workflow_search, so the agent must guess which search surface to pick.

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 exclusions, and no named alternative. The description never says to use this instead of memory or workflow search, nor what conditions make it appropriate, leaving routing entirely to inference from sibling names.

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.