Skip to main content
Glama

Caliper

by fit.caliper
OverviewDiscussionsAdmin

OBJ Analysis

format_obj
Read-onlyIdempotent

Extract metadata from an OBJ file.

Returns vertex/normal/texcoord/face counts, triangle/quad/polygon
breakdown, material and group counts, bounding box, surface area,
and triangulation status.

Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto
for payment flow details. Privacy policy: https://caliper.fit/privacy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentNoPayment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_required response. For MPP: must contain 'challenge' and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call; set only when retrying with payment).
file_b64NoBase64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
file_urlNoHTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using file_url. Max 100MB. Default: null (omit if providing file_b64 instead).
filenameNoOriginal filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment / description
      Previous value: -"x402 payment proof as a JSON string. Set this when retrying after a payment_required response. Must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' copied from the payment_required response. Example: {\"transaction\": \"0xabc...\", \"network\": \"base\", \"priceToken\": \"4:1776026505:1fe9...\"}. Default: null (omit on first call; set only when retrying with payment)."New value: +"Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_required response. For MPP: must contain 'challenge' and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call; set only when retrying with payment)."
  2. Changed4 schema fields changed
    • changedInput schema / properties / file_b64 / description
      Previous value: -"Base64-encoded file content. Use for files under 200 KB."New value: +"Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead)."
    • changedInput schema / properties / file_url / description
      Previous value: -"HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files."New value: +"HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using file_url. Max 100MB. Default: null (omit if providing file_b64 instead)."
    • changedInput schema / properties / filename / description
      Previous value: -"Original filename with extension, used for format detection when providing file_b64."New value: +"Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null."
    • changedInput schema / properties / payment / description
      Previous value: -"x402 payment proof as a JSON string. Set this when retrying after a payment_required response. Must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_required details."New value: +"x402 payment proof as a JSON string. Set this when retrying after a payment_required response. Must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' copied from the payment_required response. Example: {\"transaction\": \"0xabc...\", \"network\": \"base\", \"priceToken\": \"4:1776026505:1fe9...\"}. Default: null (omit on first call; set only when retrying with payment)."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnly and idempotent hints, so the description doesn't need to restate them. It adds valuable behavioral context by disclosing the payment requirement (x402/MPP) and pointing to format_auto for flow details, which goes beyond the annotations and informs the agent of a necessary precondition.

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 two compact paragraphs with no fluff. The first sentence front-loads the purpose, the following sentences list return metrics and payment info concisely. Every sentence serves a clear informational role, and the privacy policy line is a minor but acceptable addition.

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 the tool's purpose, return values, and payment requirements, complementing the detailed schema well. It could more explicitly clarify that this tool is for OBJ files only versus the other format_* siblings, but the tool name and first line already convey that, making the description largely complete for an agent to select and invoke correctly.

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?

All four parameters have detailed descriptions in the schema, achieving 100% coverage. The tool description itself does not add extra parameter-level meaning, so it neither compensates for gaps nor repeats schema content; this aligns with the baseline score.

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 opens with 'Extract metadata from an OBJ file', which pairs a specific verb with a well-defined resource. It then enumerates concrete return metrics (vertex counts, bounding box, surface area, etc.), clearly distinguishing it from sibling tools that target other file formats.

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 clearly establishes when to use the tool: for OBJ files, by explicitly naming the format. It also references format_auto for payment flow details, which is useful context. However, it does not explicitly name alternative tools for other formats or state when not to use this tool, so it stops short of full exclusionary guidance.

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

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