Skip to main content
Glama

Get a column's written rule

well_get_column_rule
Read-only

Read the written rule of one column: the context note stored for (target_object, target_column), resolved for the agent audience — the system note, with the workspace's own override sections applied on top.

rule.text is the resolved note, the same text the web app and the mapping prompt read. rule.source says whose text answers: system when only the standard note exists, workspace when the workspace wrote its own section over it. rule.context_hash identifies exactly the text returned. There is no rule when no context note exists at all: then the column has no written rule and you must say so rather than compose one.

The rule of one category value — what goes in "Bank fees" and what never does — is the per-value line inside the note of transactions.category_key, not a note of its own: call with target_object "transactions" and target_column "category_key", then quote only the lines that name the asked value.

Writes nothing.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
target_columnYesThe column whose written rule is read, as its MikroORM property name such as `category_key`.
target_objectYesThe object the column belongs to, an entity table name such as `transactions`.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
ruleNo
errorNo
successYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint=false, but the description adds real context beyond them: 'Writes nothing', the workspace-resolution behavior (it 'will not guess which one you mean'), and the absence case where no rule object is returned at all. That absence semantics is the kind of trap an agent would otherwise fall into by fabricating a rule.

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?

Front-loaded with the core read, then the return fields, then the two edge cases. Four paragraphs is on the long side, but each carries distinct information (resolution semantics, per-value fallback, workspace selection) rather than restating.

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 read tool with an output schema, an absence path, and multi-workspace authorization, the description covers purpose, edge cases, and workspace routing well. It leaves conversation_id and workspace_scope entirely to the schema, which is a minor gap given their behavioral weight.

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 all five parameters are already documented in the schema. The description reinforces workspace_id's conditional requirement, but adds nothing about conversation_id or workspace_scope, which the schema carries alone. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource — 'Read the written rule of one column' — and immediately defines what that rule is (the context note stored for target_object/target_column, resolved for the agent audience). It also pre-empts confusion with the per-value case, which no sibling tool name even hints at.

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?

Gives explicit when-to-use routing: call directly when the token authorizes one workspace, pass workspace_id when it authorizes several. It also explains where a category-value rule lives (a line inside transactions.category_key, not its own note) and that you must say so when no rule exists rather than compose one.

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