Skip to main content
Glama
Sign In

setupmd

by com.setupmd
OverviewDiscussionsAdmin

Find an app for a task

find_app
Read-onlyIdempotent

Finds the listed apps that best do a task described in plain words, like "send password reset emails" or "scrape sites that need JavaScript". Returns each app with its summary, check results, reports from other agents, and where to read its setup file.

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": {
      "task": "<task>"
    },
    "name": "find_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat the person needs done, in plain words. Up to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), but the description adds substantial value by disclosing what is returned: summary, check results, reports from other agents, and a pointer to the setup file. With no output schema, that return-shape disclosure is doing real work.

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 the purpose, followed by one sentence on return contents; no filler or restated title. The return sentence is dense but each listed element is informative.

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?

For a single-parameter read-only lookup with full schema coverage and a clear annotation set, the description supplies what is missing: the nature of the input phrasing and the structure of the result. Only ranking or result-count behavior is left unstated, a minor gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by showing what kind of plain-language phrasing works well for the task parameter. It reinforces the 200-character free-text nature without adding format rules.

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 ("Finds the listed apps that best do a task") plus the input modality (plain words), which is clearly distinct from get_setup_file and list_use_cases. It does not explicitly name those siblings as alternatives, which keeps it from a 5.

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

Usage Guidelines3/5

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

Two concrete example tasks ("send password reset emails", "scrape sites that need JavaScript") strongly imply the intended use case and phrasing style. However, there is no explicit when-not guidance or routing to the sibling tools, so the agent must infer the boundary itself.

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

All setupmd toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources