OneSimpleAPI

GET|HEAD /api/shortener

api_get_shortener

Destructive

Existing api/shortener API operation. Uses the OneSimpleAPI API (https://onesimpleapi.com/docs), with the same permissions, credits and storage. Supply API parameters in query or body. method defaults to GET. 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_shortener"
  }
}

Input Schema

Name	Required	Description
`body`	No	API request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
`path`	No
`files`	No	Multipart 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.
`query`	No	URL query parameters. Sensitive API options must be in body as documented by the API.
`method`	No
`headers`	No	API request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
`content_type`	No	Defaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already declare openWorld and destructive, but the description adds genuinely useful context the annotations cannot: it consumes credits, inherits the upstream API's permissions and storage, defaults to GET, preserves HTTP status/headers/body, and does not follow redirects. Minor tension remains because a "GET|HEAD" surface pairs with destructiveHint=true without explanation.

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?

Five short sentences with no filler, and the output/redirect behavior is stated crisply. The lead sentence is wasted on a restatement, but nothing is padded.

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?

For a 7-parameter tool with nested objects and no output schema, the description does well on return values (status, headers, JSON/text/base64 body, redirects) but leaves the core question of what the operation actually returns or mutates unanswered, and says nothing about error behavior.

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 71% and the schema already documents url, destination_url, files and content_type defaults. The description adds only the general rule that parameters go in query or body, without explaining the url/destination_url pairing or how body versus query is chosen beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Existing api/shortener API operation" largely restates the name and path rather than saying what the operation does (e.g. retrieve short-URL details, resolve a short link, list links). The only clarifying signal is "method defaults to GET", which is not enough to separate it from api_patch_shortener, api_delete_shortener_delete or api_post_shortener_new.

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?

The description tells the agent how to send parameters ("in query or body") but never when to choose this tool over its shortener siblings, nor what preconditions apply. No when-not guidance or alternative is named, so selection is left entirely to inference from the path.

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

All OneSimpleAPI tools Inspect

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

Need Help?