Skip to main content
Glama
Sign In

BotKelp

by io.github.aiscimi-code
OverviewDiscussionsAdmin

Get site profile

get_siteprofile
Read-onlyIdempotent

Your site profiles (privacy, terms, cookies, licence, custom_field) as JSON. list: true for names, or siteprofilename for one; field filters. Use next.arguments when a purchase reply says incomplete: true.

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": "get_siteprofile"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoIf true, return this account's profile names instead of a profile's content.
fieldNo"all" (default), or an array from: privacy, terms, cookies, license, custom_field.
cursorNoResume token from a previous incomplete result, e.g. "doc:terms".
siteprofilenameNoThe profile to fetch. Required unless list: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / account_api_key
      Removed value: -{
-  "description": "BotKelp account key (starts with \"bk_live_\"). Required.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "account_api_key"
-]
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds value beyond them: output is JSON, results are section-filterable, and incomplete results require re-entry via next.arguments. It does not describe auth needs or result size limits.

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?

Extremely compact and front-loaded: resource and return format first, then the two access modes, then the recovery hint. The telegraphic phrasing ('field filters', 'Use next.arguments') borders on cryptic but wastes no words.

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 4-parameter, non-destructive read tool with full schema coverage, rich annotations, and no output schema, the description covers resource scope, output format, and the pagination/recovery path. The unexplained 'next.arguments' and the licence/license mismatch are the only residual gaps.

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 all four parameters are already documented in the schema and the description only echoes list/siteprofilename/field. Minor inconsistency: the description spells 'licence' while the schema enum uses 'license', which could mislead an agent copying values. The 'next.arguments' reference is never tied explicitly to the cursor parameter.

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?

The description names the resource (site profiles) and enumerates the retrievable sections (privacy, terms, cookies, licence, custom_field) plus the JSON return shape, so an agent knows exactly what is fetched. The read-vs-write split with the sibling set_siteprofile is implied by name but never stated explicitly.

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

Usage Guidelines4/5

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

It states the two calling modes clearly: 'list: true for names, or siteprofilename for one', plus field filtering. It also gives a cross-tool recovery rule ('Use next.arguments when a purchase reply says incomplete: true'), which is genuine when-to-use guidance. No explicit when-not or cost/limit caveats.

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

All BotKelp toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources