Skip to main content
Glama
Sign In

VEYA

by io.github.veyanet
OverviewDiscussionsAdmin

veya_store_memory

Store agent memory for the account behind this API key. No key, no write.

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": {
      "environmentId": "<environmentId>",
      "agentId": "<agentId>",
      "data": "<data>"
    },
    "name": "veya_store_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
apiKeyNo
agentIdYes
environmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'No key, no write' usefully discloses the authentication gate (and clarifies that apiKey is effectively required even though the schema lists it as optional), but it says nothing about write durability, overwrite behavior, or what memory content is written.

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?

Two terse sentences, front-loaded with the action and the auth constraint. Nothing is wasted or padded.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, the description is far too thin. It omits what memory content means, the data/agent/environment relationship, and any return behavior.

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?

Schema description coverage is 0% across 4 parameters, so the description must compensate and largely does not. It only glosses apiKey ('behind this API key') and gestures at agent/agentId; environmentId and data remain completely undefined.

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 (store) and resource (agent memory) scoped to the API key's account, which clearly distinguishes it from veya_read_memory and veya_invalidate_memory. It does not name those siblings explicitly, so it falls just short of a 5.

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: an agent infers it should call this to persist memory. There is no explicit when-to-use vs read_memory/invalidate_memory guidance, though 'No key, no write' does hint at the prerequisite to invoke it.

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

All VEYA toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources