Skip to main content
Glama

AstraNL Coordination Protocol

create_task

Ask AstraNL to find and coordinate a verified executor for a physical task in the Netherlands. Returns an ingress receipt at once and a case once planning found a path; the client pays the executor directly; AstraNL holds no money. A step can stand on confirmed references supplied in based_on. Fee: submitting costs nothing; AstraNL charges 1 percent of the transaction only when it coordinated a completed paid task, nothing else.

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": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYeswhat must happen, in plain words
proofNowhat evidence closes the task, agreed before work starts
based_onNoReferences verified before this step is stored.
deadlineNoby when; ISO date or plain words
locationNocity or address in the Netherlands
syntheticNotrue marks a test that must never be counted or executed
budget_centsNobudget in euro cents
reply_channelNoemail or https URL where AstraNL may answer you

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With annotations only covering readOnly/openWorld/idempotent/destructive, the description supplies the operationally critical behavior an agent cannot infer: an ingress receipt returns immediately but a case only appears once planning finds a path, payment flows client-to-executor with AstraNL holding no money, and the 1% fee applies only to a coordinated completed paid task while submission is free. These are exactly the trust, money-flow and timing facts a caller needs before committing.

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 sentences, front-loaded with the core purpose and followed by return shape then commercial terms; nothing is filler. The fee sentence is long and slightly clause-heavy, but each clause carries information an agent would otherwise have to guess.

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 non-idempotent, open-world write with eight parameters and no output schema, the description covers the essential unknowns: immediate receipt versus later case, who pays whom, and when a fee is incurred. It does not address failure or rejection handling, or point to check_task for polling the resulting case, which leaves a small but real gap.

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 100%, so every parameter is already documented and the baseline is 3. The description adds one genuinely useful semantic — that steps may stand on confirmed references supplied in based_on — but leaves the remaining seven parameters (proof, deadline, budget_cents, reply_channel, synthetic) entirely to the schema.

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?

States a specific verb and resource: 'Ask AstraNL to find and coordinate a verified executor for a physical task in the Netherlands.' An agent immediately knows this creates a coordinated real-world task request, and the 'physical task in the Netherlands' scope narrows it. It stops short of naming which sibling to use instead (e.g. find_offers, check_task, coordination_contract), so differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

The geographic and physical-world scope ('a physical task in the Netherlands') implicitly tells the agent when this tool applies, and the based_on sentence hints at chained steps. There is, however, no explicit when-to-use-vs-alternative guidance, no prerequisites, and no statement of when an agent should prefer this over asking a question or checking an existing task.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources