Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_from_core_where

Read-onlyIdempotent

Retrieve rows from a core table using structured JSON conditions with AND logic. Sort and limit results as needed.

Instructions

Flexible filtering with structured JSON conditions

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>",
      "conditions": "<conditions>"
    },
    "name": "get_from_core_where"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
conditionsYesField-value pairs (AND logic), e.g., `{"type": "fp", "category": "purity"}`
limitNoMaximum rows to return
orderbyNoSort order, e.g., "name ASC" or "id DESC"

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 (readOnlyHint, idempotentHint) already indicate safe, non-destructive behavior. The description adds context about 'structured JSON conditions' but does not disclose any further behavioral traits (e.g., performance, pagination, or that results are a list). The description 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise at one sentence. It is front-loaded with the key concept of flexible filtering. However, it could be slightly expanded to include the resource ('core') without losing efficiency.

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?

Given the tool's complexity (4 parameters, nested object, no output schema) and numerous siblings, the description is insufficient. It does not explain what 'core' refers to, the expected output format, or typical use cases. The annotations compensate partially, but completeness is lacking.

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 description coverage is 100%, so the baseline is 3. The description's phrase 'structured JSON conditions' adds minimal nuance beyond the schema's 'Field-value pairs (AND logic)'. No additional meaning is provided for table, limit, or orderby.

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 states 'flexible filtering with structured JSON conditions', which clearly indicates it is used for queries with complex conditions on core data. However, it does not explicitly differentiate from sibling tools like get_from_project_where or get_from_settings_where, relying solely on the name to imply the resource.

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 description provides no guidance on when to use this tool versus alternatives such as get_from_core or other 'get_where' tools. There is no mention of prerequisites, exclusions, or typical usage scenarios.

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