Skip to main content
Glama

attach_reference

Attach source material to a post (a call transcript, an article, notes) so it is stored WITH the post and readable by the author and reviewers, WITHOUT any of it going into the post copy. Use this for anything the post was written from. NEVER paste a transcript or source text into content on save_draft/update_draft; that publishes it. Give exactly one of text (the material itself) or url (a link we fetch in the background). Makes no AI call, changes no post copy, and does not reset an approval. A post holds at most 20 references.

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": {
      "post_id": "<post_id>"
    },
    "name": "attach_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoLink to the source. We fetch the page text in the background; if it can't be fetched the link is kept.
textNoThe source material itself, stored verbatim. Max 200000 characters.
titleNoOptional label. Derived from the first line of `text` when omitted.
post_idYesPost ID to attach the reference to
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description still adds substantial context beyond them: no AI call, no post-copy mutation, no approval reset, background URL fetch behavior, and a 20-reference cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and its storage semantics, then the critical anti-pattern, then the parameter constraint and behavioral notes. No filler sentences; each clause carries operational information.

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?

Complete for a five-parameter mutation tool with no output schema and full schema coverage. It covers storage location, safety, side effects, limits, and parameter exclusivity, which is everything an agent needs to invoke it correctly.

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 100%, so baseline is 3, but the description adds real meaning: exactly one of `text` or `url` must be supplied, and URLs are fetched in the background. It correctly explains the workspace parameter's call-local scope via the schema rather than repeating it.

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 states a specific verb and resource ("Attach source material to a post") plus the exact scope (stored WITH the post, outside the post copy). It distinguishes the tool from save_draft/update_draft by explicitly warning against pasting source text into `content`.

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 when-to-use guidance ("Use this for anything the post was written from"), explicit when-not guidance ("NEVER paste a transcript or source text into `content` on save_draft/update_draft"), and names the alternatives. The one-of `text`/`url` constraint is also stated.

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