Find Runzumi references
search_mentionsFind up to 10 repositories and 10 recent job attempts in the default workspace of the user.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes |
search_mentionsFind up to 10 repositories and 10 recent job attempts in the default workspace of the user.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / items / items / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "_meta": {
- "additionalProperties": {},
- "properties": {},
- "type": "object"
- },
- "annotations": {
- "additionalProperties": false,
- "properties": {
- "audience": {
- "items": {
- "enum": [
- "user",
- "assistant"
- ],
- "type": "string"
- },
- "type": "array"
- },
- "lastModified": {
- "format": "date-time",
- "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
- "type": "string"
- },
- "priority": {
- "maximum": 1,
- "minimum": 0,
- "type": "number"
- }
- },
- "type": "object"
- },
- "description": {
- "type": "string"
- },
- "icons": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "mimeType": {
- "type": "string"
- },
- "sizes": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "src": {
- "type": "string"
- },
- "theme": {
- "enum": [
- "light",
- "dark"
- ],
- "type": "string"
- }
- },
- "required": [
- "src"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "mimeType": {
- "type": "string"
- },
- "name": {
- "type": "string"
- },
- "size": {
- "type": "number"
- },
- "title": {
- "type": "string"
- },
- "type": {
- "const": "resource_link",
- "type": "string"
- },
- "uri": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "uri",
- "type"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "icons": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "mimeType": {
- "type": "string"
- },
- "sizes": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "src": {
- "type": "string"
- },
- "theme": {
- "enum": [
- "light",
- "dark"
- ],
- "type": "string"
- }
- },
- "required": [
- "src"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "resourceUri": {
- "pattern": "\\S",
- "type": "string"
- },
- "subtitle": {
- "pattern": "\\S",
- "type": "string"
- },
- "title": {
- "pattern": "\\S",
- "type": "string"
- },
- "type": {
- "const": "resource",
- "type": "string"
- }
- },
- "required": [
- "resourceUri",
- "title",
- "type"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "_meta": {
+ "additionalProperties": {},
+ "properties": {},
+ "type": "object"
+ },
+ "annotations": {
+ "additionalProperties": false,
+ "properties": {
+ "audience": {
+ "items": {
+ "enum": [
+ "user",
+ "assistant"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "lastModified": {
+ "format": "date-time",
+ "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+ "type": "string"
+ },
+ "priority": {
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "description": {
+ "type": "string"
+ },
+ "icons": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "mimeType": {
+ "type": "string"
+ },
+ "sizes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "src": {
+ "type": "string"
+ },
+ "theme": {
+ "enum": [
+ "light",
+ "dark"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "src"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "mimeType": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "size": {
+ "type": "number"
+ },
+ "title": {
+ "type": "string"
+ },
+ "type": {
+ "const": "resource_link",
+ "type": "string"
+ },
+ "uri": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "uri",
+ "type"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "icons": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "mimeType": {
+ "type": "string"
+ },
+ "sizes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "src": {
+ "type": "string"
+ },
+ "theme": {
+ "enum": [
+ "light",
+ "dark"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "src"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "resourceUri": {
+ "pattern": "\\S",
+ "type": "string"
+ },
+ "subtitle": {
+ "pattern": "\\S",
+ "type": "string"
+ },
+ "title": {
+ "pattern": "\\S",
+ "type": "string"
+ },
+ "type": {
+ "const": "resource",
+ "type": "string"
+ }
+ },
+ "required": [
+ "resourceUri",
+ "title",
+ "type"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by disclosing result caps (10 repositories, 10 recent job attempts) and default-workspace scoping, but it omits ordering, matching behavior, and any auth or rate-limit details.
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 front-loaded sentence with no filler, so it is appropriately concise. It is perhaps slightly too terse to carry the needed usage and parameter context, but structurally it wastes nothing.
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?
The tool is simple and has an output schema plus rich annotations, which lowers the descriptive burden. Still, the description leaves important gaps around query semantics and sibling differentiation, so it is only minimally complete for selecting and invoking the tool correctly.
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 only parameter is 'query', and schema description coverage is 0%. The description does not explain query syntax, what fields are searched, or how matches are determined, so it fails to compensate for the missing schema documentation.
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 states a specific action and result set: finding up to 10 repositories and 10 recent job attempts in the default workspace. However, it never explains what a 'mention' is or what the query matches, and it does not distinguish this from siblings like search_run_logs or list_repositories.
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?
There is no explicit guidance on when to use this tool rather than list_repositories, list_runs, search_run_logs, or other search/list siblings. The default-workspace scope is mentioned, but alternatives and exclusions are not.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Last observed