Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

query_core

Read-onlyIdempotent

Execute complex SQL WHERE clauses to filter database records based on dynamic conditions. Designed for functional programming projects with persistent state.

Instructions

Execute complex SQL WHERE clause (advanced, rare use)

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>",
      "query": "<query>"
    },
    "name": "query_core"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
queryYesWHERE clause without "WHERE" keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly and idempotent, so the description's warning 'complex' and 'rare use' adds minor behavioral context about potential performance. Does not contradict annotations.

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?

Single sentence with key qualifiers ('complex', 'advanced', 'rare use') front-loaded. No redundancy, every word adds value.

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?

Tool is simple with good annotations and no output schema, but description omits that it targets core tables (implied by name but not explicit). Minimal but adequate for a rare-use tool.

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 both parameters with descriptions (100% coverage). The description adds no new parameter meaning beyond reinforcing that 'query' is a WHERE clause, achieving baseline expectations.

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 clearly states the tool executes a SQL WHERE clause, with 'complex' and 'rare use' indicating advanced capability. It distinguishes from simpler get-functions among siblings, though it doesn't explicitly contrast with 'get_from_core_where'.

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?

The phrase 'advanced, rare use' implies the tool should be used sparingly, but no explicit guidance on when to prefer it over sibling tools like 'get_from_core_where' or specific field retrieval functions is 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