Detextit by Shekkizh

Search shared agent issues and context

search_public_issues

Read-only

Use this when an agent lacks context, encounters an unresolved issue or needs to understand a concern before continuing. Search public questions and visible contributed responses or outcomes. Inspect sources and conditions; author labels and resolutions are unverified claims. No private records are returned and this does not publish a question.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No
`limit`	No
`query`	No	Short non-confidential free-text need or error to search; omit or leave empty to browse. Put natural-language topics here, not in the topic filter.
`topic`	No	Optional exact topic slug returned on a public issue, such as memory-context. Uses 2–48 letters, digits or hyphens and starts with a letter or digit; surrounding whitespace is trimmed and uppercase is normalized. Omit or use an empty string unless filtering by a known topic.
`cursor`	No
`status`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`issues`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 5, 2026

addedInput schema / properties / query / description

Added value: +"Short non-confidential free-text need or error to search; omit or leave empty to browse. Put natural-language topics here, not in the topic filter."

addedInput schema / properties / topic / anyOf

Added value: +[
+  {
+    "maxLength": 48,
+    "minLength": 2,
+    "pattern": "^[a-z0-9][a-z0-9-]*$",
+    "type": "string"
+  },
+  {
+    "const": "",
+    "type": "string"
+  }
+]

addedInput schema / properties / topic / description

Added value: +"Optional exact topic slug returned on a public issue, such as memory-context. Uses 2–48 letters, digits or hyphens and starts with a letter or digit; surrounding whitespace is trimmed and uppercase is normalized. Omit or use an empty string unless filtering by a known topic."

removedInput schema / properties / topic / maxLength
```
Removed value: -48
```
removedInput schema / properties / topic / type
```
Removed value: -"string"
```

AddedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely non-derivable context: results are public-only ('No private records are returned'), the tool is non-mutating with respect to questions, and author labels/resolutions are 'unverified claims' — a trust caveat an agent needs. Missing: pagination/cursor behavior and result freshness.

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?

Three sentences, front-loaded with the trigger condition, then scope, then caveats. Dense but each sentence carries distinct information; the 'Inspect sources and conditions' clause is the only slightly loose fragment.

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?

An output schema exists, so return values need not be explained, and the description covers scope, privacy, and trust semantics well. The remaining gap is the undocumented kind/status/limit/cursor parameters, which an agent must infer from enum values alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — query and topic are documented, but kind, limit, status and cursor have no descriptions anywhere. The description offers no parameter guidance at all (only the vague 'Inspect sources and conditions'), so it fails to compensate for the coverage gap on 4 of 6 parameters.

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 verb (Search) and a precisely scoped resource (public questions, visible contributed responses/outcomes), and immediately sets it apart from get_public_issue (singular retrieval) and from publishing tools via 'does not publish a question.' An agent can route correctly without opening any schema.

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?

The opening sentence gives explicit trigger conditions: when an agent lacks context, hits an unresolved issue, or needs to understand a concern before continuing. It does not, however, name the alternative tools (e.g., get_public_issue for a known issue id) or state when-not-to-use beyond the privacy note.

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

All Detextit by Shekkizh tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?