Skip to main content
Glama

upsert_quantum_states_batch

Batch insert or update quantum states for a specific subatomic particle, matching existing records by lowercased name to avoid duplicates.

Instructions

Batch insert or update quantum states for a specific subatomic particle matching on lower(name).

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": {
      "subatomic_particle_id": "<subatomic_particle_id>",
      "quantum_states": "<quantum_states>"
    },
    "name": "upsert_quantum_states_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantum_statesYesArray of quantum states to upsert
subatomic_particle_idYesParent Subatomic Particle ID

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 behavioral burden. It does disclose one important behavior beyond the schema: records are matched case-insensitively on name to decide insert vs update. It omits what happens to existing themes/description values on a match (merge vs overwrite), required permissions, and any return/summary information.

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 front-loaded sentence with no filler; the scope and conflict rule come before anything else. It is terse to the point that downstream details (merge semantics, results) are absent, though nothing written is wasted.

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?

This is a write operation with no annotations and no output schema, so the description must cover safety and outcome behavior. It fails to state whether matched records have themes/description replaced or merged, what the response contains, or whether the parent particle must already exist.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that the nested name field is the case-insensitive conflict key for upsert matching. It adds nothing about subatomic_particle_id beyond the schema's parent-pointer description.

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 gives a specific verb+resource pair ("Batch insert or update quantum states"), scopes it to "a specific subatomic particle", and even names the conflict key (lower(name)). It stops short of distinguishing itself from close siblings such as create_quantum_state, update_quantum_state, or populate_quantum_states_bulk.

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?

"Batch" and "upsert" imply when this is preferable to a single-record create/update, and the lower(name) match hints at conflict-tolerant loading. However, it never states when NOT to use it or which sibling to pick for single-record or bulk-populate cases, leaving the agent to infer the routing.

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