Skip to main content
Glama
Sign In

Koskamo

by com.koskamo
OverviewDiscussionsAdmin

Find task candidates

koskamo_get_task_plan
Read-onlyIdempotent

Find candidate MCP tools for a task and named host using directory evidence. Requires task and host_id; returns at most five listings per page. Pure read with no charges, installation, account grants, or execution. Task coverage and prerequisites may remain unknown.

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": {
      "task": "<task>",
      "host_id": "<host_id>"
    },
    "name": "koskamo_get_task_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask or outcome to match against published server listings.
limitNoMaximum number of candidate listings to return in this page.
cursorNoOpaque continuation cursor returned by the previous page; keep the same resource and filters.
host_idYesClient host for which setup compatibility is assessed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, but the description adds genuinely new behavioral facts: no charges, no installation, no account grants, no execution. The caveat 'Task coverage and prerequisites may remain unknown' usefully warns the agent that results are candidates, not verified matches — a reliability signal annotations cannot carry.

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?

Four short sentences with zero filler, front-loaded with the action and resource before the preconditions and caveats. Every sentence contributes a distinct fact: purpose, requirements/page size, safety profile, result uncertainty.

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?

An output schema exists, so return-value explanation is unnecessary, and pagination is covered via the limit/cursor descriptions plus the 'per page' phrasing. The only real gap is the absence of explicit routing against sibling discovery tools, which for a read-only lookup is a modest omission.

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 coverage is 100%, so the schema already documents task, host_id, limit and cursor including the host enum. The description only restates the two required params and the five-listing page cap, adding no syntax or filtering nuance beyond the schema. Baseline 3 applies.

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 and resource — 'Find candidate MCP tools for a task and named host using directory evidence' — which is far more informative than the title 'Find task candidates'. It does not name the sibling it replaces (e.g. koskamo_search_mcp_servers or koskamo_search_use_cases), so an agent must infer the boundary itself.

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?

'Requires task and host_id' establishes the invocation precondition, and the phrase 'directory evidence' hints at the discovery phase of a workflow. However, there is no explicit statement of when to prefer this over the other search/list siblings, and no when-not guidance.

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

All Koskamo 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