Skip to main content
Glama

Record Filter Replacement Date

set_crm_lifecycle
Destructive

Calculate and store a filter replacement recommendation from driving patterns. Writes a hashed identifier, vehicle and recommendation date. This is a date record, not a scheduled task, SMS, email or notification service.

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": {
      "user_id": "<user_id>",
      "car_model": "<car_model>",
      "driving_time_or_freq": "<driving_time_or_freq>"
    },
    "name": "set_crm_lifecycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
car_modelYes
driving_distanceNo모름
driving_time_or_freqYes

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?

The description correctly discloses the write behavior ("Writes a hashed identifier, vehicle and recommendation date"), consistent with readOnlyHint=false, and adds a useful privacy detail that the identifier is hashed — context the annotations do not carry. It never addresses destructiveHint=true: an agent cannot tell whether a prior recommendation is overwritten, what is lost, or what is returned. For a destructive write with no output schema, that is a meaningful gap.

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?

Three short sentences, front-loaded with the action and resource, then the write payload, then the disambiguation. Nothing is padded; the exclusion sentence earns its place given the name/behavior mismatch.

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 4-parameter destructive write with no output schema and zero schema coverage, the description covers intent and write behavior but omits what the return looks like, whether re-invocation overwrites existing records, and any format requirements for the inputs. Enough to avoid gross misuse, not enough to call it confidently.

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%, so all meaning must come from the description, and it only loosely maps fields (hashed identifier → user_id, vehicle → car_model, driving patterns → driving_time_or_freq). It gives no format for driving_time_or_freq, no explanation of the driving_distance parameter or its Korean default "모름", and no statement that all three required fields must be supplied. The compensation is partial at best.

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 supplies a concrete verb pair ("calculate and store") plus a specific resource ("filter replacement recommendation from driving patterns"), which is essential because the tool name 'set_crm_lifecycle' is opaque and actively misleading. It also disambiguates by declaring what it is not (scheduled task, SMS, email, notification). It stops short of naming a sibling it competes with, so an agent must still infer routing among get_hvac_filter_info, check_environment, etc.

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 exclusion sentence ("not a scheduled task, SMS, email or notification service") is real guidance — it prevents an agent from invoking this expecting reminder delivery. However, there is no positive when-to-use condition and no pointer to an alternative tool for the cases it rules out, so motivation and timing must be inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources