Skip to main content
Glama

request_cell

Submit a missing calculation need so stemseal can create a matching deterministic cell; receive a ticket and return later once demand builds.

Instructions

Tell the hub that you needed a calculation and no cell fit. This is how new cells get made: you get a ticket, and the cell is built as demand gathers, so come back next time. Describe the need in one or two sentences.

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": {
      "need": "<need>"
    },
    "name": "request_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the key point: this is asynchronous and non-immediate, yielding a ticket while the cell is built 'as demand gathers,' so the agent must return later. It omits any permission/auth requirements, deduplication behavior for repeat requests, or what the ticket response contains.

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?

Three short sentences that are front-loaded with the core action and the consequence. The closing instruction about the parameter is useful, though 'so come back next time' is conversational filler that 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?

For a one-parameter tool with no output schema and no annotations, the description covers the essentials an agent needs: when to call it, that the result is deferred via a ticket, and how to phrase the input. It stops short of explaining how to later retrieve the built cell, which would close the loop.

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?

The single 'need' parameter has 0% schema description coverage, so the description must compensate. It does partially by telling the agent to 'describe the need in one or two sentences,' giving content and length guidance, but it adds no format, granularity, or example detail beyond that.

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 gives a concrete verb and outcome: it reports a needed calculation that no existing cell covers, which results in a ticket and a future cell. That implicitly separates it from find_cell/list_cells (search) and call_cell (execute), though it never names those siblings. The metaphor ('hub', 'cell', 'ticket') is loose but the actionable meaning is unambiguous.

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 states a clear triggering condition: use this when you needed a calculation and 'no cell fit.' It does not explicitly instruct the agent to exhaust find_cell first or name the alternatives, so the ordering guidance is implied rather than spelled out.

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

Deploy Server

Other Tools