marketplace

Call an endpoint

call_endpoint

Execute one endpoint of a marketplace API through the live gateway. Requires a JoJ API key configured on this MCP connection as an HTTP header (Authorization: Bearer jk_...). Usage is billed to the key's subscription exactly like any other API call.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	The endpoint path exactly as listed by get_api.
`slug`	Yes	The API's marketplace slug.
`method`	Yes	HTTP method of the endpoint.
`arguments`	No	Endpoint arguments keyed by parameter name, as documented by get_endpoint (path/query/form/header parameters and, when documented, a `body` object).

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing side effectsasha. It mentions authentication and billing, giving some behavioral clarityverträglich. However, it does not state potential side effects of the API call (e.g., data modification), error handling, or rate limits. For an execution tool, this is partial transparency.

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?

The description is concise, consisting of two focused sentences that convey the action, authentication requirement, and billing implications. No redundancy or fluff.

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?

The description covers essential context: what the tool does (executes endpoint), required auth setup, and billing. It also implicitly instructs the agent to refer to get_api and get_endpoint for path and argument details. It does not mention output format or error behavior, but for an API execution tool this may be acceptable given the schema and sibling references.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides thorough descriptions for all four parameters. The path references get_api, arguments references get_endpoint, and slug and method are clearly defined. This leverages sibling tools for complete documentation, ensuring the agent knows exactly how to supply each parameter.

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?

The description clearly states the tool's function: 'Execute one endpoint of a marketplace API through the live gateway.' It specifies the verb (execute) and resource (endpoint of a marketplace API), and distinguishes it from sibling tools like get_api or search_apis by focusing on execution rather than listing or retrieving metadata.

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?

The description provides context for when to use the tool (to execute an actual API call) and notes the prerequisite of a JoJ API key. It does not explicitly exclude cases or point to alternatives, but the mention of live gateway and billing implies these are production calls grants clear usage context. Could be improved with explicit statements like 'use get_endpoint to inspect parameters first'.

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

All marketplace tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool has a clear, non-overlapping purpose: one searches for APIs, two provide metadata (overview vs. endpoint docs), and one executes calls. The distinction between get_api and get_endpoint is well defined by scope (API-level vs endpoint-level).

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (call_endpoint, get_api, get_endpoint, search_apis) with only minor deviation: 'search' instead of 'get' for the search tool, which is conventional. The pattern is clear and predictable.

Tool Count5/5

With only 4 tools, the set is tightly scoped to the marketplace's purpose: discovering, documenting, and executing APIs. Each tool is essential for the core workflow, and 4 is a reasonable number for this domain.

Completeness4/5

The surface covers the main lifecycle: search to find, get_api to understand, get_endpoint for details, call_endpoint to execute. Missing features like authentication management or plan/subscription management are external to the core usage, so this is a minor gap.

Resources

Need Help?