Odile Labs

Open a request

open_request

Open a request for one customer's job at one business, so assistants can hand it to each other with the customer's say-so. Use it first when another assistant may need to continue the job; for a one-off message or booking, use send_to_business alone. It contacts nobody and books nothing. Returns request_id, customer_link and your grant (scope book). Show the customer link (customer_link) to the person before acting: it is how they see the request, revoke an assistant and issue a handoff code. Treat it as private. Then book with send_to_business, passing request_id. Requires direct:tasks.

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": {
      "biz": "<biz>",
      "objective": "<objective>",
      "customer_name": "<customer_name>",
      "callback_number": "<callback_number>"
    },
    "name": "open_request"
  }
}

Input Schema

Name	Required	Description
`biz`	Yes	Business id from the card that find_business_agent returned.
`objective`	Yes	What the customer wants done and when.
`customer_name`	Yes	The customer's name.
`callback_number`	Yes	The customer's number in E.164, for example +15615550123.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 2, 2026
- addedInput schema / properties / biz / description
```
Added value: +"Business id from the card that find_business_agent returned."
```
- addedInput schema / properties / callback_number / description
```
Added value: +"The customer's number in E.164, for example +15615550123."
```
- addedInput schema / properties / customer_name / description
```
Added value: +"The customer's name."
```
- addedInput schema / properties / objective / description
```
Added value: +"What the customer wants done and when."
```
- addedInput schema / properties / objective / properties / service / description
```
Added value: +"The service wanted, in plain words."
```
- addedInput schema / properties / objective / properties / window / description
```
Added value: +"When the customer wants it, in plain words."
```
AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description clarifies crucial behavioral points like it 'contacts nobody and books nothing,' what the output contains (request_id, customer_link), and that the operation must be treated as private.

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?

The tool is highly detailed, but the information is logically structured: Purpose -> When/When-Not -> Workflow -> Constraints. It is efficient, though dense.

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?

It is exceptionally complete, not only detailing the inputs but also explaining the usage of the outputs, such as using 'customer_link' to show the request to the customer before proceeding with the booking via send_to_business.

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?

Since schema coverage is 100%, the schema provides full semantic detail on all 4 parameters. The description mentions the data captured (like business and customer info) but adds no value beyond what is already fully documented in the input schema.

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 description clearly identifies the specific resource being acted upon (a customer's job) and the action (open a request). It clearly positions the tool within the workflow of assistant handoffs.

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?

It provides explicit usage constraints: Use it when handing off a job to another assistant, and explicitly advises against using it for one-off messages, directing the agent to the correct alternative tool (send_to_business).

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

All Odile Labs tools Inspect

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

Need Help?