Skip to main content
Glama

call_api

Access Choson conjoint API /v1 routes for searches, optimization, segments, survey design, and MaxDiff or volumetric studies; send JSON bodies and poll queued results.

Instructions

Any other /v1 route (see api_reference): searches (range, recommend, test-next; queued, poll with GET on the same path), optimize, segments, MBC / MaxDiff / volumetric / concept tools, survey design. path is relative to /v1, e.g. "/fits/abc123/range". JSON only; use upload_data and download for files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes
methodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits — JSON-only payloads, `path` is relative to /v1, and search routes are queued and must be polled with a GET on the same path — but it never addresses that `method` can issue mutating requests, nor authentication, error semantics, or what comes back from a raw route.

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?

It is a single dense sentence plus a constraint clause, front-loading the 'any other route' scope before the examples. The nested parentheticals ('queued, poll with GET on the same path') are slightly cluttered but each packs genuinely useful information.

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 generic passthrough with three parameters, no annotations and no output schema, the description covers the essential scoping (path base, JSON payload, async polling) but leaves the response contract and the meaning of `method` entirely implicit. An agent could invoke it, but would be guessing about writes and return shape.

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 0%, so the description must compensate: it does for `path` (relative to /v1, with a concrete example '/fits/abc123/range') and implicitly for `body` ('JSON only'). The `method` parameter is never mentioned, so its accepted values and defaults are undocumented everywhere.

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 description states this is a catch-all passthrough for 'Any other /v1 route' and enumerates the resource families it covers (searches, optimize, segments, MBC/MaxDiff/volumetric/concept, survey design), so an agent can tell it apart from dedicated siblings like start_fit or price_sweep. It lacks a crisp verb+resource formulation because the verb is caller-supplied via `method`, but the scope is unmistakable.

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?

It routes the agent to api_reference when looking for a route and explicitly excludes file operations ('use upload_data and download for files'), which is real alternative-selection guidance. It stops short of saying when a dedicated sibling should be preferred over crafting a raw path, but 'any other' implies that ordering.

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