Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

search_docs

Read-onlyIdempotent

Search SunLicense documentation by query for SDKs, marketplace integrations, offline licenses, API, and CLI, returning matching sections with links for setup and troubleshooting.

Instructions

Search the SunLicense documentation (SDKs, marketplace integrations, offline licenses, API, CLI) and return the matching sections with links.

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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYeswhat to look for, e.g. 'offline license fallback' or 'BuiltByBit placeholder'

Output Schema

NameRequiredDescriptionDefault
moreYeswhere the docs are
pagesNomatching pages, when the docs' full text can't be read
sectionsNomatching sections of the docs, best first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral fact beyond that: results are 'matching sections with links' rather than whole documents. It says nothing about result counts, ranking, or query limits, which is acceptable given an output schema exists.

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 sentence that front-loads the action and resource and then lists coverage areas, with no redundant restatement of the title or annotations. Every clause earns its place.

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?

The tool is simple (one required string), annotations are rich, and an output schema exists, so the description need not explain return shape. It adequately conveys what corpus is searched, with only minor gaps around result volume or ranking behavior.

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?

With a single parameter at 100% schema description coverage, the schema already explains the query field and supplies two example queries. The description adds no syntax, phrase-matching, or scoping guidance beyond what the schema provides, so the baseline of 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?

The description gives a specific verb (Search) and resource (the SunLicense documentation) and enumerates the covered areas (SDKs, marketplace integrations, offline licenses, API, CLI). This clearly separates it from the sibling licensing/CRUD tools, though it does not name any sibling explicitly.

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?

Usage is only implied: an agent can infer it should call this when it needs documentation answers rather than license data. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative (e.g. offline_license_file for generating a file versus reading about it).

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