Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_from_core

Read-onlyIdempotent

Retrieve records from a database table by providing an array of IDs; an empty array returns all records.

Instructions

Get records by ID(s), or all records if empty array

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>",
      "id_array": "<id_array>"
    },
    "name": "get_from_core"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
id_arrayYesArray of integer IDs to fetch, **empty array [] returns ALL records**

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe and idempotent behavior. The description adds value by specifying that an empty id_array returns all records, which is beyond what annotations provide. No contradictions.

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?

The description is a single sentence that is front-loaded with the action 'Get records...' and contains no unnecessary words. It is appropriately sized and earns its place.

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?

Given the simplicity of the tool (two parameters, high schema coverage, annotations present, no output schema), the description covers the core behavior. It could mention the return format or that it only works on core tables, but it is largely complete for an agent to understand usage.

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%, with both parameters already well-described in the input schema (table as 'Table name', id_array with empty array behavior). The tool description does not add any additional parameter-level information beyond the schema.

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?

The description clearly states the tool fetches records by ID(s) or all records if the array is empty. The verb 'Get' and resource 'records from core' are specific. Among siblings like 'get_from_core_where' and 'get_from_project', this tool is distinguished by its retrieval method (by IDs or all).

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 description implies usage for fetching records by IDs or all, but it does not explicitly mention when to use this tool versus alternatives like 'get_from_core_where' for filtered queries. No exclusions or alternative tool names are 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