Skip to main content
Glama

Find Tools

sirv_find_tools
Read-onlyIdempotent

Searches this server's tool list by plain-language task to find the right Sirv AI Studio tool, returning ranked matches with summaries and credit cost. Use when unsure; it runs nothing.

Instructions

Find the right Sirv AI Studio tool for a task. Give the task in plain words in query, such as "remove background" or "shopify image".

Call it first when you are not sure which of this server's tools fits. When you already know the tool, call that tool directly.

It only searches this server's tool list: it runs no tool, calls no Studio API and changes nothing.

Returns up to limit tools (default 5), best match first, each with its name, title, a one-sentence summary and whether it spends credits. An empty list means that no tool matched: read tools/list instead.

Credits: free.

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": "sirv_find_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost tools to return, 1 to 10. Default: 5
queryYesThe task in plain words, such as 'remove background', 'shopify image' or 'product alt text'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, but the description goes further by stating it runs no tool and calls no Studio API, and by disclosing the return shape (name, title, one-sentence summary, credit cost), the default limit, and what an empty list means. The only redundancy is "changes nothing", which largely restates destructiveHint=false.

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?

Front-loaded with purpose, then ordering guidance, then scope, then return shape, then cost – a good priority order with short paragraphs. Minor waste in restating the schema's query examples and in "Credits: free." as a standalone line, but no sentence is filler.

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

Completeness5/5

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

For a two-parameter discovery tool with no output schema, the description covers everything an agent needs: what it does, when to pick it over a direct tool call, that it is side-effect free, what the result items contain, the default result count, and the empty-result fallback.

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%, so both query and limit are already documented with examples and bounds; the description's "Give the task in plain words in query, such as 'remove background'" repeats the schema's own examples. It adds nothing about query phrasing strategy or how matching works, so the baseline 3 applies.

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?

"Find the right Sirv AI Studio tool for a task" names a specific verb (find) and resource (this server's tool list), and immediately frames itself as a meta/discovery tool rather than a Studio action. Nothing in the sibling list can be confused with it because it explicitly scopes itself to searching the tool list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Call it first when you are not sure which of this server's tools fits") and an explicit when-not-to-use with the alternative ("When you already know the tool, call that tool directly"). It also handles the failure path by naming tools/list as the fallback when the result set is empty.

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