Skip to main content
Glama
Sign In

OneSimpleAPI

by com.onesimpleapi
OverviewDiscussionsAdmin

GET /api/divide_by_zero

api_get_divide_by_zero
Destructive

Return the joke: Friends don't let friends divide by zero. Uses the OneSimpleAPI API (https://onesimpleapi.com/docs), with the same permissions, credits and storage. Supply API parameters in query or body. This tool always uses GET; do not supply method. Outputs preserve HTTP status, headers and JSON/text/base64 body; redirects are returned without following them.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoAPI request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
pathNo
filesNoMultipart uploads keyed by API field name (for example pdf). Supply file_name, base64 bytes and optional mime_type. Uploads use the existing API file validators.
queryNoURL query parameters. Sensitive API options must be in body as documented by the API.
headersNoAPI request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
content_typeNoDefaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 (openWorld, destructive, non-idempotent), and the description adds genuine context beyond them: shared permissions/credits/storage, auth and transport headers managed by the connection, and that redirects are returned unfollowed rather than resolved. It never explains why a joke GET carries destructiveHint=true, leaving a mild tension between the described trivial read and the declared hazard.

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?

The payload of the definition (what is returned) is front-loaded in the first sentence, with the connection and transport caveats trailing behind. It is compact for the number of caveats covered, though the permission/credits/storage sentence is generic enough to feel like filler.

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 specifies what a response preserves (HTTP status, headers, JSON/text/base64 body) and how redirects behave, which is exactly the return-value information an agent needs. For a zero-required-parameter endpoint that is close to complete; only the destructive annotation goes unexplained.

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 83%, so the schema already documents body, query, files, headers and content_type in detail. The description only restates the query-or-body choice and the 'do not supply method' rule, adding little meaning the schema does not already carry — 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 first sentence names the concrete result — 'Return the joke: Friends don't let friends divide by zero' — which is a specific verb plus resource and is unmistakable against the other api_* siblings. It falls short of a 5 only because the surrounding text is generic connection boilerplate rather than further distinguishing this endpoint's role.

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?

It gives operational guidance ('Supply API parameters in query or body', 'This tool always uses GET; do not supply method'), which prevents a real invocation error. However, it offers no when-to-use or when-not-to-use framing versus the many sibling endpoints, so an agent gets invocation rules but not selection guidance.

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

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