Skip to main content
Glama
Sign In
xgmem

xgmem

by meetdhanani17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_graph_observations

Add new observations to existing entities in a project knowledge graph to update agent memory.

Instructions

Add new observations to existing entities in the project knowledge graph.

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": {
      "projectId": "<projectId>",
      "observations": "<observations>"
    },
    "name": "add_graph_observations"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project identifier
observationsYesAn array of observation objects to add to graph entities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, description only states action. Fails to disclose behavioral traits such as whether observations are appended or overwritten, or requirements for entity existence.

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?

One concise sentence with no wasted words. Front-loaded purpose. Could be slightly more structured but effective.

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 simple tool with 2 params and no output schema, missing guidance on return value and behavior (e.g., error on missing entity). Adequate but with gaps.

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 coverage is 100% with parameter descriptions. Description adds 'new' and 'existing' but these are already implied. Provides minimal extra value beyond schema.

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?

Description clearly states verb 'add' and resource 'observations to existing entities in project knowledge graph'. Distinguishes from sibling tools like create_entities and create_relations.

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?

No explicit guidance on when to use this tool vs alternatives like create_entities or delete_observations. Implied by name but not clarified.

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

Deploy Server

Other Tools