Skip to main content
Glama

upsert_subatomic_particles_batch

Batch insert or update subatomic particles under a particle group, matching on lowercased name to prevent duplicate entries.

Instructions

Batch insert or update subatomic particles under a specific particle group 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": {
      "particle_group_id": "<particle_group_id>",
      "subatomic_particles": "<subatomic_particles>"
    },
    "name": "upsert_subatomic_particles_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
particle_group_idYesParent Particle Group ID
subatomic_particlesYesArray of subatomic particles to upsert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 genuinely useful trait: matching happens on lower(name), i.e. case-insensitive name-based upsert rather than ID-based. It says nothing about atomicity, partial-failure behavior for the array, permission requirements, or what the call returns, which are material gaps for a mutation tool.

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

Conciseness5/5

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

A single sentence with the resource and scope front-loaded and the matching rule trailing as the qualifier. No filler, no repetition of the schema, and nothing an agent would skim past.

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 mutation tool with no annotations and no output schema, the description covers what the tool does and how records are matched, which is the most important part. It leaves out what the response looks like (inserted vs updated counts), whether the batch is transactional, and what happens on duplicate names within the array.

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 description coverage is 100%, so the schema already documents particle_group_id and the items array, making 3 the baseline. The description adds real meaning on top: the group is the parent scope, and the match key for deciding insert-versus-update is lower(name) — semantics the schema does not express anywhere.

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+resource: batch insert-or-update of subatomic particles, scoped to a particle group. That is well beyond restating the name. It stops short of naming the single-record siblings (create_subatomic_particle / update_subatomic_particle), so an agent must infer the batch-vs-single distinction.

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?

The word 'Batch' implies this is the bulk path versus single-record create/update, which is usable context. But there is no explicit statement of when to choose this over upsert_particle_groups_batch or populate_subatomic_particles_bulk, and no prerequisites or failure conditions are given.

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