Skip to main content
Glama

Carrick

by io.github.carrick-tools
OverviewDiscussionsAdmin

Browse indexed functions and intents

list_function_intents
Read-onlyIdempotent

List indexed functions with their one-line intents, paginated; filter by service or substring. The index covers every function with an intent, not just exported ones. Use it to browse what a service contains or compare what sibling repos have built. Pass file to answer "what can I call in this file" without reading it, with compact for signature-only rows. For concept queries ('dedupe users by email'), use search_by_intent instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath suffix of the file to list functions from (e.g. `src/oauth2/service.ts` or `service.ts`). Matched on whole segments, so `gin.ts` never matches `login.ts`.
repoNoYour repo as owner/repo (git remote) or just the repo name. Resolves which Carrick project to query.
limitNoMax functions per page (default 50, max 200). The full org haystack is too large to return inline.
offsetNoNumber of functions to skip before this page (default 0). Pass the `next_offset` from a previous call to page through.
compactNoReturn signature-only rows (name, signature, line span, first sentence of the intent) instead of full detail. Use it with `file` to read what a file offers at a fraction of the source.
projectNoCarrick project slug to query. Omit to auto-resolve via `repo`, or omit both when the workspace has one project.
serviceNoFilter to a specific service (omit for all services)
typed_onlyNoWhen true, return only functions whose signature is fully explicit (every param and the return annotated).
name_containsNoCase-insensitive substring filter on the function name.
exclude_serviceNoService to exclude from results (use this when looking for sibling-repo implementations of work in your current service)
intent_containsNoCase-insensitive substring filter on the intent text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is met. The description adds real context beyond them: pagination behavior, that the index includes non-exported functions, and the reason for the limit cap ('the full org haystack is too large to return inline'). It does not mention auth or project-resolution failure modes, so it falls short of a 5.

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?

Dense but front-loaded: capability, then scope, then the file/compact recipe, then the sibling routing. Every sentence earns its place, though the file/compact clause is slightly packed and could be split for readability.

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 11 optional params, no output schema, and 100% schema coverage, the description supplies the paging model, the filter surface, and the sibling alternative, which is most of what an agent needs. It leaves project/repo auto-resolution to the schema descriptions, which is acceptable.

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?

Schema coverage is 100%, so the baseline is 3, but the description still adds value: the file+compact combination is explained as a way to read a file's surface, and it flags exclude_service as the sibling-repo lever. These are usage-level semantics the schema alone doesn't convey.

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?

States a specific verb and resource (list indexed functions) plus the scope of the index ('every function with an intent, not just exported ones'). It explicitly distinguishes itself from the sibling search_by_intent, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete scenarios ('browse what a service contains or compare what sibling repos have built'), a file-scoped recipe, and an explicit exclusion routing concept queries to search_by_intent. When-to-use and when-not-to-use are both covered.

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

All Carrick toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources