Skip to main content
Glama

knack

by io.usefulapi

List fields for an object

knack_list_fields
Read-only

List the fields of ONE object as [{ key, name, type, required }]. Fetches GET /applications/{app_id} and returns the fields of the object whose key === objectKey (e.g. "object_1"). app_id defaults to the configured KNACK_APPLICATION_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoOptional Knack Application ID; defaults to the configured KNACK_APPLICATION_ID.
objectKeyYesThe Knack object (table) key, e.g. "object_1".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that it fetches the entire application and filters locally, providing important behavioral context about efficiency and API usage.

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?

Three clear, front-loaded sentences with no waste; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even without an output schema, the description includes the output format and explains the filtering logic, making it self-contained for this read-only list tool.

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

Parameters4/5

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

With 100% schema coverage, both parameters are described in schema; the description adds the default behavior for appId, increasing semantic value.

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 it lists fields for one object with output format, but does not explicitly distinguish from sibling tools like knack_list_objects or knack_get_application.

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 use for retrieving fields of a single object but does not provide when-not-to-use or alternative tools, leaving guidance implicit.

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

All knack toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct operation: CRUD for records, listing fields/objects/records, fetching application schema, and a generic request. No overlap in purpose.

Naming Consistency4/5

All tools use 'knack_' prefix with verb_noun pattern (create_record, delete_record, etc.). The exception is 'knack_request' which lacks a verb, causing slight inconsistency.

Tool Count5/5

9 tools is well-scoped for a Knack integration, covering essential CRUD, listing, schema retrieval, and an escape hatch.

Completeness4/5

Core CRUD operations are present, plus listing and schema. Missing batch operations or advanced filtering, but the generic request tool fills some gaps.

Resources