Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_settings_entry

Add a new entry to a user settings database table by providing the table name and field-value pairs.

Instructions

Add entry to user settings database

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": {
      "table": "<table>",
      "data": "<data>"
    },
    "name": "add_settings_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
dataYesField-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations indicate non-read-only and non-destructive, which aligns with 'add'. Description adds 'user settings' context but doesn't disclose idempotency, duplicate handling, or permission requirements.

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?

Single sentence with no waste, but may be too minimal for full understanding. Efficient but could benefit from slight elaboration.

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 2-param tool with nested objects and no output schema, the description leaves many unanswered questions (e.g., valid table names, data format constraints, return value). Incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with basic descriptions. Description adds no additional meaning about expected values or constraints beyond schema.

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?

Description clearly states verb (Add) and resource (entry to user settings database), distinguishing it from update or delete siblings. However, 'entry' is ambiguous and could be more specific, e.g., 'row'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like add_user_setting or update_settings_entry. No prerequisites or exclusions provided.

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