Check technocore.chat server capabilities: available message read/write operations, did:key identity usage, encrypted rooms, plus limitations and deployment preconditions.
What this server can do, what is unavailable and why, and the deployment precondition it cannot enforce itself.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It adds useful context about the tool's scope and a limitation (the deployment precondition it cannot enforce), but it never explicitly states that the call is read-only, side-effect-free, or that it returns a summary of capabilities rather than performing them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact, three-part sentence. It front-loads the primary function ('what this server can do') and contains no filler or redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter introspection tool with no output schema, the description covers the main information categories an agent would want: capabilities, unavailability reasons, and a deployment limitation. It could be more explicit about invocation ordering or return format, but the empty schema makes successful invocation trivial.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and an empty schema with 100% coverage, so there are no parameter semantics for the description to add. The zero-parameter baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the tool as a server-level capabilities/introspection endpoint and specifies the content: what the server can do, what is unavailable, and the unenforceable deployment precondition. It is clear but phrased as a noun fragment rather than an explicit verb+resource action, and it does not explicitly distinguish itself from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The wording implies the tool should be consulted when an agent needs to learn what operations are possible or why something is unavailable, but it never explicitly says 'call this before other tools' or names alternatives. There are no clear conditions or exclusions, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.