Skip to main content
Glama
Sign In
sechscamp

sechscamp

by minntelligence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_topic

Load a specific VC6 topic by id or name to retrieve sourced markdown or factual answers. Resolve questions about dates, location, tickets, wifi, cell, nudity, and more.

Instructions

Load one VC6 topic by id or name (e.g. dates-location, tickets, wifi-cell, nudity) and return sourced markdown or facts.

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": {
      "topic": "<topic>"
    },
    "name": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic id or name from list_topics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that the tool returns sourced markdown or facts and is a load, but it does not mention behavior for missing/unknown topics, authentication, or reading vs mutation beyond the verb 'load'.

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?

One compact sentence front-loads the action ('Load one VC6 topic') and includes concrete examples with no filler. Every phrase 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 with a single well-documented parameter. Without an output schema, the description compensates by stating the return type ('sourced markdown or facts'). It could add not-found behavior, but the essentials are covered.

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 description need not re-document the 'topic' parameter. It adds useful example topic names, but not much deeper semantic meaning, so baseline 3 is appropriate.

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

Purpose5/5

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

States a specific operation ('Load one VC6 topic') with clear retrieval keys (id or name) and output ('sourced markdown or facts'). The verb and 'one' distinguish it from list/search/ask siblings.

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?

Implies use when you already have a topic id or name, and the schema points to list_topics, but the description never names alternatives or says when to use search_vc6/ask_vc6 instead. Guidance is only implicit.

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