Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

find_solutions

Read-only

The solutions registry — 740+ third-party API services and tools (gateways, portals, testing, monitoring, …) ranked by adoption across the companies API Evangelist tracks.

Input Schema

NameRequiredDescriptionDefault
qNoFree text over title, summary, tags, and body.
pageNoPage number, 1-based (default 1). Use with `limit` to walk a long list.
sortNoOrder when there is no `q`: "default" (dated content newest first, the rest A-Z), "title" (A-Z) or "date" (newest first). A `q` always orders by relevance.
tagsNoTag slugs; match any by default.
limitNoResults per page, 1-100 (default 25).
matchNoHow multiple `tags` combine: "any" (default, at least one) or "all" (every tag).any
fieldsNoReturn only these keys on each record, e.g. ["slug","title","url"].
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"Return only these keys on each record, e.g. [\"slug\",\"title\",\"url\"]."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / sort / description
      Added value: +"Order when there is no `q`: \"default\" (dated content newest first, the rest A-Z), \"title\" (A-Z) or \"date\" (newest first). A `q` always orders by relevance."
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context — corpus size (740+) and the adoption-based ranking across tracked companies — but says nothing about how ranking behaves when q is empty, result limits, or scope of coverage. Adequate but not rich.

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?

A single front-loaded sentence that wastes no words. It is efficient, though the ellipsis-truncated enumeration ('gateways, portals, testing, monitoring, …') adds little and the sentence reads as a catalog label rather than an actionable tool statement.

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?

With an output schema absent and eight parameters (all documented), the description is functionally sufficient to attempt a call. However, for a search tool that coexists with several similarly named find_* siblings, the lack of routing guidance leaves a real gap for correct tool selection.

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 all eight parameters (q, page, sort, tags, limit, match, fields, context) are already documented in the schema itself. The description adds no parameter-level meaning, 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?

The description clearly identifies the resource pool: a registry of 740+ third-party API services and tools ranked by adoption. It conveys what an agent will find, but never states the operative verb (search/list/filter) nor distinguishes this registry from the sibling find_services and find_tools registries.

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?

No guidance on when to use find_solutions versus find_services, find_tools, or find_related — all of which could plausibly be chosen for the same discovery intent. There are no exclusions, prerequisites, or selection criteria offered.

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

All api-evangelist toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources