get_server_infoRetrieve server identity, version, and description to verify the SRC MCP server is running correctly.
Get SRC server identity, version, and description. Use to verify the MCP server is running correctly.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format | text |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| meta | Yes | ||
| error | No | ||
| message | No | ||
| success | Yes | ||
| schema_version | Yes |
Changes observed during successful MCP inspections.
v2.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "description": {
+ "type": "string"
+ },
+ "fullName": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "fullName",
+ "version"
+ ],
+ "type": "object"
+ },
+ "error": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "meta": {
+ "additionalProperties": false,
+ "properties": {
+ "bounded": {
+ "const": true,
+ "type": "boolean"
+ },
+ "confidence": {
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+ },
+ "coverage": {
+ "enum": [
+ "precise",
+ "approximate",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "generated_at": {
+ "type": "string"
+ },
+ "index_freshness": {
+ "enum": [
+ "fresh",
+ "stale",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "instruction_signals": {
+ "additionalProperties": false,
+ "properties": {
+ "count": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "detected": {
+ "type": "boolean"
+ },
+ "kinds": {
+ "items": {
+ "enum": [
+ "instruction_override",
+ "authority_spoofing",
+ "tool_execution_request",
+ "secret_exfiltration_request",
+ "delimiter_spoofing",
+ "hidden_unicode",
+ "encoded_instruction"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "scan_truncated": {
+ "type": "boolean"
+ },
+ "scanned_bytes": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "signals": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "column": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "confidence": {
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+ },
+ "kind": {
+ "enum": [
+ "instruction_override",
+ "authority_spoofing",
+ "tool_execution_request",
+ "secret_exfiltration_request",
+ "delimiter_spoofing",
+ "hidden_unicode",
+ "encoded_instruction"
+ ],
+ "type": "string"
+ },
+ "line": {
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "type": "integer"
+ },
+ "offset": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "reason": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "kind",
+ "line",
+ "column",
+ "offset",
+ "confidence",
+ "reason"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "detected",
+ "count",
+ "kinds",
+ "signals",
+ "scanned_bytes",
+ "scan_truncated"
+ ],
+ "type": "object"
+ },
+ "local_only": {
+ "const": true,
+ "type": "boolean"
+ },
+ "provenance": {
+ "enum": [
+ "local-analysis",
+ "local-filesystem",
+ "local-index",
+ "local-lsp"
+ ],
+ "type": "string"
+ },
+ "source_is_untrusted": {
+ "type": "boolean"
+ },
+ "source_revision": {
+ "type": "string"
+ },
+ "truncated": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "generated_at",
+ "local_only",
+ "bounded",
+ "provenance"
+ ],
+ "type": "object"
+ },
+ "schema_version": {
+ "const": 1,
+ "type": "number"
+ },
+ "success": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "schema_version",
+ "success",
+ "meta"
+ ],
+ "type": "object"
+}v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds semantic context that the tool returns server identity, version, and description, which goes beyond the annotations and helps the agent anticipate the content. It does not contradict any annotation, and while it omits details like authentication or rate limits, the simplicity of the operation and the annotation coverage keep the gap minimal.
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 two short sentences with zero filler. The primary purpose ('Get SRC server identity, version, and description') is front-loaded, followed immediately by the usage context. Every word contributes to the agent's understanding, achieving an ideal balance of brevity and informativeness.
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: one optional parameter with full schema documentation and an output schema already defined. The description provides the purpose and a concrete usage scenario, which is all an agent needs to decide when to call it and what to expect. For a read-only informational tool with no side effects, nothing essential is missing.
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 input schema provides 100% coverage for the single 'format' parameter, including an enum ('json'/'text'), a default, and a description. The description itself adds no parameter-specific information, but since the schema fully documents the parameter, the baseline of 3 is appropriate. The description's mention of 'identity, version, and description' does not clarify the format parameter's effect, though it is not required to.
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 verb ('Get'), a clear resource ('SRC server'), and the exact data returned ('identity, version, and description'). It also gives an explicit use case ('verify the MCP server is running correctly'), which makes the tool's purpose unmistakable. No sibling tool overlaps with this informational role, so it is well differentiated.
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 description explicitly says 'Use to verify the MCP server is running correctly,' which gives a clear when-to-use scenario. It does not mention any alternatives or exclusions, but none of the sibling tools serve a similar purpose, so the guidance is sufficient. A perfect score would require explicit when-not conditions, which are not present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.