Skip to main content
Glama
Sign In

One Coworking

by com.onecoworking.www
OverviewDiscussionsAdmin

Not for me

decline_option

Optional: record that the person said one option is not for them, and why (price, too_small, too_large, location, look_and_feel, amenities, contract_terms, availability, chose_another, not_moving_now, other). Use only what the person told you. It goes to their broker; nothing is sent to the space, and the option stays on their link. Option handles come from get_request_status.

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": {
      "access_key": "<access_key>",
      "option": "<option>",
      "reason": "<reason>"
    },
    "name": "decline_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
optionYes
reasonYes
access_keyYesThe access key confirm_email_code returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the destination of the write (goes to the broker), what does NOT happen (nothing is sent to the space), and the side effect on the recipient's experience (the option stays on their link). That is exactly the kind of non-obvious consequence an agent needs before mutating state.

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 action and the safety-relevant facts come first, with the long enum list quarantined in a parenthetical so it doesn't bury the main point. The inline enumeration is bulky but arguably earns its place as a vocabulary hint.

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 4-parameter mutation tool with no output schema and sparse schema descriptions, the description covers the crucial unknowns: optionality, provenance of the option handle, and downstream visibility. The only material gap is the undocumented 'note' parameter.

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 coverage is only 25%, so the description has to compensate. It adds real meaning for 'option' by explaining that handles come from get_request_status, and it mirrors the reason enum values, but it says nothing about the 'note' field, leaving one of four parameters undocumented in both places.

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 names a specific action (recording that a person rejected an option) and enumerates the reason taxonomy, which makes the intent unmistakable. It doesn't explicitly contrast itself with siblings like rate_viewing, but the 'not for them' framing is distinct enough that confusion is unlikely.

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 signals optionality ('Optional: ...'), gives a data-quality constraint ('Use only what the person told you'), and points to get_request_status as the source of option handles. It stops short of explicit when-not-to-use or naming an alternative tool, so it is clear context rather than full routing guidance.

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

All One Coworking 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