Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_projects_pull

Pull a project's connector snapshot on demand to retrieve institutions and waitlist data into the kernl memory layer.

Instructions

Pull the project's connector snapshot now (institutions, waitlist).

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": {
      "project": "<project>"
    },
    "name": "kernel_projects_pull"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. It does not disclose whether this triggers a remote sync (side effects, cost, latency, rate limits), whether it is idempotent, or what happens if the connector is unavailable — all critical for a verb as ambiguous as "pull."

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?

One short sentence with the action and scope front-loaded; nothing is wasted. It is under-specified rather than bloated, but the phrasing is efficient.

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

Completeness3/5

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

For a one-parameter tool with no output schema the definition is minimal but not incoherent — the parenthetical tells the agent roughly what data is involved. Still missing the read-vs-trigger distinction and project identifier format, which matter for correct invocation.

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

Parameters2/5

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

Schema coverage is 0% for the single required parameter, so the description must compensate and does not. It never states whether "project" expects an ID, slug, or display name, nor how to obtain a valid value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Pull the project's connector snapshot now" gives a verb and resource, and the parenthetical hints at the payload (institutions, waitlist). However, "pull" is ambiguous — it could mean fetch the current snapshot or trigger a refresh/sync — so an agent cannot tell what operation actually occurs or what it changes.

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 word "now" implies this forces an immediate snapshot rather than reading a cached or scheduled one, which is faint usage context. There is no statement of when to prefer this over kernel_projects_get or kernel_projects_list, and no prerequisites or exclusions.

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