Skip to main content
Glama

add_npc

Add a non-player character to the knowledge graph with name, description, role, status, traits, and current location. Use it to track story characters and their whereabouts.

Instructions

Add a new character (NPC) to the 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": {
      "npc": "<npc>"
    },
    "name": "add_npc"
  }
}

Input Schema

NameRequiredDescriptionDefault
npcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv0.6.0
    • removedInput schema / properties / npc / properties / abilities
      Removed value: -{
      -  "description": "Specific skills or powers the NPC possesses",
      -  "items": {
      -    "description": "Item in abilities array",
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / npc / properties / alignment
      Removed value: -{
      -  "description": "The ethical or moral alignment of the NPC",
      -  "type": "string"
      -}
    • removedInput schema / properties / npc / properties / background
      Removed value: -{
      -  "description": "The background story of the NPC",
      -  "type": "string"
      -}
    • changedInput schema / properties / npc / properties / currentLocation / description
      Previous value: -"The current location of the NPC"New value: +"Where the character is now (the location must already exist)"
    • changedInput schema / properties / npc / properties / description / description
      Previous value: -"A detailed description of the NPC"New value: +"Who the character is: appearance, personality, background"
    • removedInput schema / properties / npc / properties / gender
      Removed value: -{
      -  "description": "NPC's gender",
      -  "type": "string"
      -}
    • removedInput schema / properties / npc / properties / importance
      Removed value: -{
      -  "description": "The importance of the NPC in the story or world",
      -  "type": "string"
      -}
    • removedInput schema / properties / npc / properties / money
      Removed value: -{
      -  "description": "Currency or wealth the NPC holds",
      -  "type": "string"
      -}
    • removedInput schema / properties / npc / properties / motivation
      Removed value: -{
      -  "description": "The driving purpose or goals of the NPC",
      -  "type": "string"
      -}
    • changedInput schema / properties / npc / properties / name / description
      Previous value: -"NPC's name"New value: +"The character's unique name"
    • removedInput schema / properties / npc / properties / origin
      Removed value: -{
      -  "description": "The origin location of the NPC",
      -  "items": {
      -    "description": "Item in origin array",
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / npc / properties / race
      Removed value: -{
      -  "description": "NPC's race",
      -  "type": "string"
      -}
    • removedInput schema / properties / npc / properties / reputation
      Removed value: -{
      -  "description": "How the NPC is perceived by others",
      -  "type": "string"
      -}
    • changedInput schema / properties / npc / properties / role / description
      Previous value: -"NPC's role or occupation"New value: +"Occupation or role in the story, e.g. blacksmith, villain"
    • removedInput schema / properties / npc / properties / secret
      Removed value: -{
      -  "description": "A hidden detail about the NPC",
      -  "type": "string"
      -}
    • changedInput schema / properties / npc / properties / status / description
      Previous value: -"NPC's current status"New value: +"The character's current condition"
    • addedInput schema / properties / npc / properties / status / enum
      Added value: +[
      +  "alive",
      +  "injured",
      +  "dead",
      +  "missing"
      +]
    • changedInput schema / properties / npc / properties / traits / description
      Previous value: -"Unique traits or characteristics of the NPC"New value: +"Personality traits or notable characteristics"
    • changedInput schema / properties / npc / required
      Previous value: -[
      -  "name",
      -  "role",
      -  "status",
      -  "currentLocation",
      -  "description"
      -]New value: +[
      +  "name",
      +  "description"
      +]
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that – notably it does not say what happens on a duplicate character name, whether referenced locations must pre-exist, or whether the call fails or overwrites.

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?

One short sentence with no waste and the action front-loaded, but it is arguably undersized for a mutation tool taking a nested object. Nothing is buried, yet nothing extra is provided.

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?

For a write operation on a nested object with no output schema, the definition omits duplicate-name handling, the pre-existing-location constraint, and what the return value contains. The annotations cover the safety flags, but the behavioral contract an agent needs to call this correctly is missing.

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?

Top-level parameter coverage is 0%: the single 'npc' object has no description in the schema, so the description should compensate and does not. The nested fields (name, role, status enum, traits, description, currentLocation) are self-documented in the schema, including the constraint that currentLocation must already exist, but the description repeats none of this or adds emphasis.

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?

States a specific verb ('Add') and resource ('a new character (NPC)') plus the destination ('the knowledge graph'), which cleanly separates it from delete_npc and update_npc. It lacks any further scope detail, but the core action is unambiguous.

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 only implied by the verb and the sibling naming convention; there is no explicit statement of when to prefer this over update_npc (for existing characters) or add_nodes. An agent can infer the split, but the definition does not spell it out.

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