AskEditor

Get editor link

get_editor_url

Read-onlyIdempotent

[read] The project's links. url opens it in AskEditor: the one to hand the person. pane_url is the same editor with its own chat closed (null only for a talking film): if your app has a built-in browser pane, open it there so the person watches the edit beside this conversation. Pass pane: true when you are about to open that pane: the answer then carries browser_handoff.url, which opens it already signed in. That link works once, for two minutes; open it in the pane and never show it. A pane is only ever opened on a link from this tool, never on an address you wrote yourself.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_editor_url"
  }
}

Input Schema

Name	Required	Description	Default
`pane`	No	True when you are about to open the editor in a browser pane beside the chat: adds browser_handoff.url, the one-time link that opens the pane already signed in.
`project_id`	Yes	The AskEditor project (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses non-obvious traits: pane_url is null only for a talking film, browser_handoff.url is single-use and expires in two minutes, and that link must never be shown to the person. These are exactly the operational and safety constraints an agent could not infer from annotations or schema.

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 read-only marker and the core purpose are front-loaded, and every sentence carries real information (pane semantics, expiry, secrecy, the single-source-of-links rule). The middle sentences are dense and slightly run-on, which costs a point.

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?

There is no output schema, and the description fully compensates by naming each returned field (url, pane_url, browser_handoff.url) and its semantics, including the null case and link lifetime. An agent has everything needed to call it and handle the response correctly.

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% and the schema already explains both `pane` and `project_id`, including the browser_handoff.url consequence. The description largely restates the pane trigger, adding only emphatic framing rather than new parameter-level meaning, so the baseline 3 applies.

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 states plainly that this returns the project's editor links and immediately disambiguates the two return fields (url vs pane_url). It is clearly distinct from siblings like open_project, read_project, or create_editor_project, though the opening line ('The project's links') is terser than a full verb+resource statement.

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 gives explicit triggering conditions ('Pass pane: true when you are about to open that pane'), a routing rule ('if your app has a built-in browser pane, open it there'), and a hard exclusion ('A pane is only ever opened on a link from this tool, never on an address you wrote yourself'). Nothing about when to use this tool versus alternatives is left to inference.

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

All AskEditor 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?