USERDATA

tag

Apply a named label with a note to a filing, fact, ticker, or note to categorize research records for later retrieval.

Instructions

Tags a "filing" (accession), "fact" (fact_id), "ticker" or "note".

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": {
      "tag_name": "<tag_name>",
      "target_type": "<target_type>",
      "target_id": "<target_id>",
      "note_text": "<note_text>"
    },
    "name": "tag"
  }
}

Input Schema

Name	Required	Description	Default
`tag_name`	Yes
`note_text`	Yes
`target_id`	Yes
`target_type`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It implies a mutation but never states whether tags are additive or replace existing tags, whether the call is idempotent, whether it requires the target to pre-exist, or what happens on a duplicate tag.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, which is good, but the heavy quoting and embedded parentheticals make it read as a schema fragment rather than a clear statement of purpose. It is terse to the point of being cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters, zero schema coverage, and no annotations, the description is far too thin for the tool's complexity. An output schema exists so return values need not be explained, but the mutation semantics and the meaning of two required parameters remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all four required parameters depend on the description. It partially compensates by mapping target_type values and hinting at target_id formats (accession for filings, fact_id for facts), but tag_name and note_text get no explanation at all, and the ticker/note cases have no id format hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "tags" plus an enumeration of target kinds (filing, fact, ticker, note) gives a rough idea of the operation, and the parenthetical identifier hints help. But it never says what a tag is (label? annotation? classification?) or what effect it has, and it is not clearly distinguished from siblings like add_note or add_to_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to tag versus when to use add_note, add_to_list, or define_concept, all of which are adjacent in the sibling list. No prerequisites (e.g., target must already exist) or exclusions are stated.

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

tag