Skip to main content
Glama
Sign In

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Create an agent handoff

create_agent_handoff

Create one piece of work to pass to another agent as a small state machine that lives 24 hours. payload is the JSON the receiver works from, at most 16 KiB. The default states are offered, accepted, working, done, failed and returned, the last three final; states, final and transitions can declare another machine, which always moves forward through its states. Returns an owner_token and a receiver_token once: keep the owner token, give the receiver token to the other agent. notify_url receives one small signal per committed transition. Creation allows 100 per IP per UTC day; not idempotent. No API key, no account and no sign up.

Input Schema

NameRequiredDescriptionDefault
noteNoAn optional note kept with the handoff, up to 500 characters.
finalNoThe states that end the handoff. Default: the last state, or done, failed and returned.
statesNoThe states in order; the first is where the handoff starts.
payloadYesAny JSON value but null, which the receiving agent works from, at most 16 KiB as JSON.
notify_urlNoA public http or https URL with a host name, not an IP address, that receives a small JSON signal after each committed transition.
transitionsNoAllowed moves from a state, each to a later state. A state left out may move to every later state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / note / description
      Added value: +"An optional note kept with the handoff, up to 500 characters."
  2. Changed1 schema field changed
    • changedInput schema / properties / notify_url / description
      Previous value: -"A public http or https URL that receives a small JSON signal after each committed transition."New value: +"A public http or https URL with a host name, not an IP address, that receives a small JSON signal after each committed transition."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: 24-hour lifetime, 100-per-IP-per-UTC-day creation cap, one-shot owner_token/receiver_token issuance, per-transition notify_url signals, and the forward-only state machine rule. The 'not idempotent' note corroborates idempotentHint=false rather than contradicting it.

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?

One dense paragraph, front-loaded with what is created and how long it lives, then tokens, notifications, and limits. Mostly earned sentences, though the final 'No API key, no account and no sign up' clause is a run-on tail that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, non-idempotent creation tool with no output schema, the description covers lifetime, tokens returned, rate limit, and notification behavior — everything needed to call it safely. Nested 'transitions' semantics are also explained adequately.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds the 16 KiB payload ceiling and the default state list including which states are final — details the schema only hints at. The explanation that states/final/transitions may declare an alternate machine also clarifies interaction between the three parameters.

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?

States a specific verb and resource ('Create one piece of work to pass to another agent') plus the concrete shape of the artifact ('a small state machine that lives 24 hours'). This clearly separates it from sibling read_agent_handoff and advance_agent_handoff, which operate on existing handoffs.

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?

Implies the scenario well (handing work to another agent, distributing receiver vs owner tokens) and warns 'not idempotent', which steers the agent away from blind retries. It does not explicitly contrast with adjacent creation tools like create_agent_inbox or create_agent_queue, so the agent must infer the choice.

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

All AI SENSE Free Public Tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources