Skip to main content
Glama

Folk MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List people

folk_list_people
Read-only

List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page (1-100, default 20).
cursorNoPagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
filterNoStructured filter: attribute → operator → value, expanded to filter[attribute][operator]=value query keys. Example: {"firstName":{"eq":"John"}}.
combinatorNoHow to combine multiple filters — 'and' (all must match) or 'or' (any). Default 'and'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / filter / additionalProperties / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / filter / additionalProperties / additionalProperties / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds only that pagination and structured filters are supported and cites the REST endpoint, without disclosing auth requirements, rate limits, or default result shape beyond what the schema covers.

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?

Two short sentences, capability and endpoint, with zero filler and the list/filter scope front-loaded. Every clause 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?

With no output schema, the description could have said more about the returned page shape, but the cursor parameter already explains pagination.nextLink. For a 4-param, zero-required read tool with full schema coverage, the definition is essentially complete.

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 limit, cursor, filter, and combinator are all fully documented in the schema itself. The description's 'cursor pagination and structured filters' adds framing but no meaning beyond the schema, matching the baseline 3.

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?

States a specific verb+resource ('List/filter people (contacts)') and adds the mechanics it supports, so it is clearly distinct from folk_list_companies, folk_list_groups, and folk_list_users. No explicit sibling contrast sentence, which keeps it just below a 5.

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 listing purpose implies when to reach for it versus folk_get_person, and the mention of cursor pagination hints at multi-page retrieval, but there is no explicit when-to-use/when-not guidance or named alternative. Usage is inferred rather than stated.

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

All Folk MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources