Skip to main content
Glama

Batch Create Entries

batch_create_entries

Create up to 50 journal entries in one batch for imports or bulk project-memory creation, with per-entry types, scores, and context links.

Instructions

Create multiple journal entries at once. Max 50 per batch. Use this for imports or bulk creation. Select the most accurate entry_type for each. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id. REQUIRED: You MUST include impact_score, trust_score, and validation_status. REQUIRED: You MUST use related_to to anchor entries to previous context.

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": "batch_create_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesNo
auto_indexNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_numberNoNumeric project ID applied to batch entries when omitted per item.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
countNo
errorNoHuman-readable error message
detailsNoAdditional error context
entriesNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
indexStatusesNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • changedInput schema / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / project_number
      Added value: +{
      +  "description": "Numeric project ID applied to batch entries when omitted per item.",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • removedInput schema / properties / use_test_db
      Removed value: -{
      -  "type": "boolean"
      -}
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the agent knows this mutates and may duplicate; the description adds the 50-item cap, which is real value. But it offers nothing on atomicity or partial-batch failure for a batch write, which is the central behavioral question, and its three 'REQUIRED' mandates misstate the contract in ways that will mislead an agent.

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?

The strongest facts (count, bulk use case) are front-loaded and the piece is short. However, three near-identical 'REQUIRED: You MUST...' sentence openers consume most of the text and encode incorrect contract information rather than compressing useful guidance.

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?

Nuance: an output schema exists, so return values need not be explained. What is missing for a batch mutation with a 24-property nested item schema is failure semantics (partial success?), how top-level workspace_id/project_number default into entries, and correct parameter requirements, some of which the description actively misstates.

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?

With only 50% schema description coverage the description should compensate, but instead it contradicts the schema: project_number is declared 'REQUIRED' while the schema documents it as optional and 'workspace_id is preferred'. It also references a 'related_to' parameter that does not exist (the schema uses relationships[].relationType), and mandates impact_score/trust_score/validation_status that the schema marks optional and describes with its own scales.

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 and resource plus a concrete bound: 'Create multiple journal entries at once. Max 50 per batch.' The batching scope implicitly separates it from the singular create_entry, but no sibling is named outright, so an agent must infer that this is the bulk counterpart.

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?

'Use this for imports or bulk creation' gives a usage context, but there is no when-not guidance and no alternative routed to (create_entry, team_batch_create_entries, or import_markdown are never mentioned). The embedded 'Extract this by querying memory://agent-id' is a workflow hint rather than selection guidance.

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