Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

higgsfield

Read-only

Higgsfield, read-only: its models, the price of a job, and the state of a job. Nothing here spends the balance.

op:

  • list_models — the models the key can call: slug (what model takes, e.g. higgsfield-ai/soul/v2/standard for stills, kling-video/v3.0/pro/image-to-video, bytedance/seedance-2.5/image-to-video for clips), title, description, output_type (image, video), operation_type (text2image, image_edit, text2video, image2video, video2video…). Filter with output_type, operation_type and search (words in slug, title or description). No parameter schema is given: each model's page at docs.higgsfield.ai lists its parameters, and estimate names a missing or faulty one.

  • estimate — the price of a generation, free and with no effect: model and the same params as the generation. Answers usd (null when no amount can be read, basis says why), approximate (true when read from a per-second price sentence: it prices a 16:9 output before discount) and the raw estimate.

  • get_request — one job (request_id): status queued, in_progress, completed, failed (with error), nsfw or canceled. Once completed, outputs lists every file address and expires_at says when they are deleted (seven days after the end). Failed, nsfw and canceled jobs are not charged. On the shared key, only a job your organization submitted (job_not_found).

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": {
      "op": "<op>"
    },
    "name": "higgsfield"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesWhat to read (see above).
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
fullNo`list_models`: the raw records instead of the tightened view.
modelNo`estimate`: the model slug from `list_models`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
paramsNo`estimate`: the model's own parameters, e.g. {"prompt": "…", "image_url": "https://…", "duration": 5, "resolution": "720p"}.
searchNo`list_models`: words that must all appear in the slug, title or description.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
request_idNo`get_request`: the job's id, from `higgsfield_act` op='create_generation'.
output_typeNo`list_models`: only image or only video models.
operation_typeNo`list_models`: only models doing this, e.g. image2video.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses cost semantics (estimate is free, failed/nsfw/canceled jobs are not charged), output lifecycle (`expires_at` seven days after completion), degraded-result semantics (`usd` null with `basis`, `approximate` derived from a per-second price sentence), and a shared-key visibility restriction returning `job_not_found`. These are exactly the behaviors an agent cannot infer from the schema.

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?

Front-loads the read-only/no-spend guarantee, then organizes remaining detail as one bullet per `op` in the same order as the enum. Dense but zero filler — every clause is either a filter rule, a return field, or a caveat.

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 13-parameter, no-output-schema tool it documents the returned fields per op (slug/output_type/operation_type, usd/approximate/raw estimate, status/outputs/expires_at/error), which substitutes for a missing output schema. The gaps are minor: `full` and the identity/routing parameters (_org, _group, _run_id, _project, _instance) are left to the schema.

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?

With 100% schema coverage the baseline is 3, and the description earns the bump by adding real meaning: concrete slug examples per output type, the `params` object semantics (same shape as the generation, with an example payload), and the interaction where `estimate` names a missing or faulty parameter. The `full` flag is left entirely to the schema, which keeps it off a 5.

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 opening sentence names the resource (Higgsfield models, job price, job state) and the scope constraint ("read-only... Nothing here spends the balance"), and the per-op bullets make each of the three verbs concrete. Against the sibling higgsfield_act, the read-only framing plus the pointer to `higgsfield_act` op='create_generation' makes the division of labour unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each op carries explicit when-to-use guidance: `list_models` to discover slugs and filter by output_type/operation_type/search, `estimate` because it is "free and with no effect" before spending, `get_request` to poll one job. It also names the alternative tool (higgsfield_act) for actual generation and supplies an exclusion ("On the shared key, only a job your organization submitted").

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

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