Skip to main content
Glama
Sign In
maviapi

maviapi

by kuzenlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search maviapi APIs

search_apis
Read-onlyIdempotent

Find ready-made structured JSON APIs for websites or topics, including sites without official APIs, to use as data endpoints; leave query empty to list all.

Instructions

Find a ready-made maviapi API for a website or topic, e.g. "hotels", "flights", "booking.com" or "turkish news". maviapi turns websites that have no official API into structured JSON endpoints, and monitors and repairs them when the site changes. Leave query empty to list every API. Next step: get_api, to see an API's endpoints and parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWebsite, domain, or topic to look for. Empty lists everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world (openWorldHint=false), and the description is consistent with that catalog-scoped read. It adds genuinely useful domain context beyond the annotations: that APIs are generated from sites lacking official APIs and are monitored and repaired when sites change, which tells the agent results can be maintained rather than stale. It does not cover result ordering, ranking, or result-set size limits, which keeps it below a 5.

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?

Three short sentences, front-loaded with the purpose, then the product context, then the routing hint. Nothing is padded and the alternative workflow pointer sits at the end where an agent will look for it.

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 one-optional-parameter read tool with rich annotations and no output schema, the description covers purpose, input semantics, and the follow-up call. No safety, permission, or prerequisite information is missing.

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% and the single parameter is fully documented in the schema, so the baseline is 3. The description adds meaning beyond it by illustrating acceptable input granularity — a bare topic ("hotels", "flights"), a domain ("booking.com"), or a topical phrase ("turkish news") — while the empty-query behavior largely restates the schema.

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?

States a specific verb and resource ("Find a ready-made maviapi API") plus the scope of what can be searched (website or topic), with concrete example queries. It also distinguishes itself from get_api by framing that tool as the follow-up for endpoints and parameters, so an agent can route between them without inspecting schemas.

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

Usage Guidelines4/5

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

Gives explicit entry conditions (searching for a ready-made API for a site or topic) and an explicit degenerate case ("Leave `query` empty to list every API"), plus a recommended next step (get_api). It stops short of stating when a search is not the right approach (e.g. what to do if no match is found), so it is clear but without exclusions.

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

Deploy Server

Other Tools