Skip to main content
Glama
Sign In

lcas

by cloud.lcas
OverviewDiscussionsAdmin

Find tools

find_tools
Read-onlyIdempotent

Find single MCP tools or A2A skills that do something, across all agents. Only endpoints that passed lcas's last daily check. Ordered by reliability, not by a score: endpoints whose weekly live test passed first, then by days working in the last 30, then by how well the words match. Each result has the endpoint to connect to and its check history.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain ID: 1 = Ethereum, 8453 = Base. Omit for both.
limitNo
moneyNoMoney hint on the tool's own text: moves funds, asks for payment, or reads prices/balances. Word matches, not verified.
queryYesWords to match in tool or skill names and descriptions, e.g. "weather forecast".
serviceNoOnly MCP tools or only A2A skills.
tested_onlyNoOnly endpoints whose last weekly live test passed.
tool_findingsNoTool-poisoning scan of tools' own text (instruction phrasing aimed at the reading app, invisible Unicode, asks for secrets or to send data out, orders about other tools). exclude = hide matches, only = show only matches. Patterns catch lazy attacks only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tool_findings
      Added value: +{
+  "description": "Tool-poisoning scan of tools' own text (instruction phrasing aimed at the reading app, invisible Unicode, asks for secrets or to send data out, orders about other tools). exclude = hide matches, only = show only matches. Patterns catch lazy attacks only.",
+  "enum": [
+    "exclude",
+    "only"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A3.7/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, non-destructive, non-open-world), yet the description adds real behavior: results are restricted to endpoints passing a daily check and are ordered by verified reliability rather than by a score. It also discloses what each result contains, which goes beyond the annotations.

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?

Four tight, front-loaded sentences; the scope statement comes first, then the eligibility filter, then the ordering rule. The ordering sentence is long but each clause carries distinct information.

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?

With no output schema, the description usefully says results include the endpoint to connect to and its check history, and explains the ordering so an agent can interpret sequence. Minor gaps remain around result shape details, but nothing critical for invoking it correctly is missing.

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 86%, so the schema already documents nearly every parameter including enums for service, money, and tool_findings. The description only reinforces that matching is word-based, adding little new meaning beyond what the schema provides.

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 — find single MCP tools or A2A skills across all agents — which implicitly distinguishes it from the agent-oriented sibling search_agents. It never names a sibling explicitly, so differentiation relies on inference.

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?

Implies usage (locate a tool/skill that does something) and states a selection constraint (only endpoints that passed the last daily check), but gives no explicit when-not guidance or named alternative such as search_agents or get_agent.

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

All lcas 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