Skip to main content
Glama
Sign In

OneSimpleAPI

by com.onesimpleapi
OverviewDiscussionsAdmin

POST /api/image_info

api_post_image_info
Destructive

Extract EXIF metadata from images including camera info, GPS coordinates, and timestamps 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_image_info"
  }
}

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 flag this as a mutating, non-idempotent, open-world call, and the description adds genuinely new context: it shares 'permissions, credits and storage' with OneSimpleAPI (so calls consume credits), it never follows redirects, and it returns raw HTTP status, headers and JSON/text/base64 bodies. What is missing is any statement of error behavior or how a failed extraction is surfaced, but the credit and redirect disclosures are above the annotation baseline.

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?

Purpose is front-loaded in the first clause, and the remaining sentences cover transport, credits, redirects and response shape without filler. The middle section ('with the same permissions, credits and storage') is slightly under-explained and could be tightened.

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 six optional parameters, nested body/query/files objects and no output schema, the description does the heavy lifting an agent needs: it explains the HTTP-shaped return value, redirect handling, and that the API options retain their original OneSimpleAPI meaning. The notable gap is that required is empty, yet an image URL is effectively mandatory for extraction, and the description never says so.

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 coverage is 83%, so the schema already documents url, output, files, headers and content_type, and the description adds little beyond noting that API options may go in query or body. The one real addition is the negative rule 'do not supply method', plus the reminder that sensitive options belong in body; that is useful but thin against a well-documented 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?

Opens with a specific verb and resource: 'Extract EXIF metadata from images including camera info, GPS coordinates, and timestamps', which lets an agent tell this apart from a generic image manager at a glance. It stops short of naming a sibling it is not (e.g., api_post_image_manager), so differentiation relies on the reader knowing what the siblings do.

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?

Usage is implied by the purpose (use this when you need EXIF/camera/GPS data out of an image), and the description adds a real invocation constraint: 'This tool always uses POST; do not supply method.' There is no explicit guidance on when to prefer a different image endpoint, nor any stated prerequisite such as needing a reachable image URL.

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