Skip to main content
Glama

save_profile

Create or replace a persistent tender-search profile in SQLite so saved criteria are available immediately and can override built-in or startup profiles with the same name.

Instructions

Create a persistent MCP profile or replace it with overwrite=true.

    criteria contains TOML profile fields except name, such as cpv, exclude_cpv,
    keywords_any, regions or deadline_days. Replacing uses the full new criteria.
    Profiles are saved in this server's SQLite database and visible immediately.
    A saved profile can override a built-in or startup-file profile with the same 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": {
      "name": "<name>",
      "criteria": "<criteria>"
    },
    "name": "save_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
criteriaYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses persistence in the server's SQLite database, immediate visibility, that replacement discards the old criteria in favor of the full new set (a destructive nuance), and the precedence effect over built-in and startup-file profiles. Missing only permission/auth notes and the concrete failure mode when a name already exists without overwrite=true.

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?

Front-loaded with the core action and overwrite rule, followed by short, purposeful sentences. The stitched-in TOML block is slightly awkward in formatting but every line adds information; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the key unknowns of a free-form criteria object and overwrite semantics. What remains thin is the name parameter's constraints and the error behavior on duplicate names, plus lack of any permission context for a write tool with no annotations.

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 0%, so the description must compensate, and it does for the hardest parameter: criteria is described as TOML profile fields excluding name with concrete examples (cpv, exclude_cpv, keywords_any, regions, deadline_days), which clarifies the otherwise free-form nested object. overwrite is explained by the replacement condition; name is left implicit but its meaning is self-evident.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (create/replace) and resource (persistent MCP profile), and explicitly ties the replace behavior to overwrite=true. An agent can tell save_profile apart from delete_profile in the sibling list without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear selection rule: use this tool to create, or with overwrite=true to replace, and notes that a saved profile overrides a built-in or startup-file profile of the same name. It stops short of naming alternatives (e.g. delete_profile or the tools that consume profiles) or stating what happens on a name collision without overwrite.

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