Skip to main content
Glama

Tulsa Ecosystem Map

List kinds

list_kinds
Read-onlyIdempotent

List the kinds with browse pages, entry counts and page citations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_kinds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is in disclosing the payload: browse pages, entry counts and page citations. That tells an agent what it will actually receive, which matters since there is no output schema. It stops short of covering ordering, exhaustiveness or empty-result behavior.

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?

A single front-loaded sentence with no filler. Every clause contributes information about the returned content, so nothing reads as padding.

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?

For a simple, parameterless list tool with rich annotations, the definition is close to sufficient: it says what the resource is and what each item contains. Only minor operational details (ordering, whether the list is exhaustive, pagination) are absent, and these are low-risk for a small enumeration of kinds.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to clarify. The schema is trivially complete (empty object), and the description correctly adds no parameter noise.

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 ('List the kinds') and clarifies the scope by naming the data returned (browse pages, entry counts, page citations). It is distinguishable from get_kind (single retrieval) and from the unrelated list_categories/list_tags, though it never explicitly contrasts with a sibling.

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 verb 'list' implies use when an enumeration of kinds is wanted, which is adequate for a zero-parameter tool. However, there is no explicit guidance about when to prefer this over get_kind (detail for a single kind) or whether other list tools should be used alongside it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources