OneSimpleAPI

POST /api/color

api_post_color

Destructive

Generate unique colors from text or convert between color formats, with palette suggestions 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 POST; 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_post_color"
  }
}

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.
`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.

AddedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructive/non-idempotent/openWorld, so the bar is lower, yet the description adds real context: it names the upstream service and notes shared permissions, credits and storage, and it explains that HTTP status, headers and body are preserved, and redirects are returned unfollowed. It does not say anything about credit consumption per call or rate limits, which would matter for a metered proxy.

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?

Front-loads the capability statement before the boilerplate about the upstream API, which is the right order. It is a little dense and the sentence about the OneSimpleAPI API is generic boilerplate repeated across this family, but no sentence is purely redundant.

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?

For a schema-driven POST proxy with no output schema, the definition covers transport semantics, mutation status, response passthrough and redirect handling, which is what an agent needs to invoke it safely. The main gap is the absence of any statement about what a successful color payload contains or the cost of a call.

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 83%, so the baseline is 3, but the description adds genuinely useful meaning by explaining that the same API parameters may be supplied via query or body, and that one body field accepts either free text or a hex/RGB value. It also clarifies that headers such as Idempotency-Key are managed by the connection only indirectly through the schema.

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?

Names a specific capability set: generate unique colors from text, convert between color formats, and suggest palettes. That is far more specific than the title's bare 'POST /api/color' and clearly distinguishes it from the cache, email, PDF and image siblings. It stops short of 5 only because the two modes are not separated into discrete operations.

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?

Gives operational rules ('Supply API parameters in query or body', 'This tool always uses POST; do not supply method') but no guidance on when to pick this over another tool, nor on when to prefer the text-generation path versus the format-conversion path. Usage is implied by the text parameter's dual role rather than stated.

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?