Skip to main content
Glama
蓝汐 · 潮汐认知图谱

蓝汐 · 潮汐认知图谱

by A16Nights

cg_goal

List, create, or update long-term goals and todos in a hard-protected goals layer, tracking status, priority, progress, and details without deleting stored memory.

Instructions

列出或创建/更新长期目标与待办(存储在 goals 层,默认硬保护)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cg_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoupsert 更新已有目标时传入
opNo操作:list(默认)或 upsert
titleNo目标标题
statusNo状态
contentNo目标详情
priorityNo优先级
progressNo进度 0~100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context by disclosing the storage layer and that entries are 'hard-protected by default', which signals mutation risk, but it never explains what hard protection actually entails, whether upserts are reversible, or what happens to existing fields on update.

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?

A single compact sentence, front-loaded with the operations and the resource, with no filler. It is arguably over-terse for a 7-parameter tool, but nothing in it is wasted.

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

Completeness3/5

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

For a 7-parameter dual-mode tool with no annotations and no output schema, the description covers purpose and storage/protection level but leaves the list-vs-upsert decision, permission requirements, and return behavior to inference. It is adequate but has clear gaps for an agent invoking upsert.

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 every parameter (id, op, title, status, content, priority, progress) is already documented in the schema, including the enum meanings and that id is only needed for upsert updates. The description adds no syntax, defaults, or constraints beyond what the schema already states; 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 names specific verbs (list, create/update) and a specific resource (long-term goals and todos), plus where they live (the goals layer). An agent can tell this apart from generic memory siblings like cg_write/cg_read because the resource is explicitly goals/todos, but no sibling is named for direct contrast.

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

Usage Guidelines3/5

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

Usage is implied: the two operations (list vs upsert) and the fact that list is the default are discoverable, which tells an agent when to call with no arguments. There is no explicit guidance on when to prefer this over cg_write/cg_update for general memory, nor any stated prerequisites or exclusions.

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