Subastech — subastas judiciales de inmuebles (BOE)

Mi cuenta

mi_cuenta

Read-onlyIdempotent

Tu plan, cuota de informes, funciones disponibles, scopes del token, límites de uso y URLs útiles (precios, integraciones). Requiere cuenta (scope cuenta:read).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mi_cuenta"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`cta`	No
`org`	No
`plan`	Yes
`urls`	Yes
`token`	Yes
`limites`	Yes
`usuario`	Yes
`funciones`	Yes
`disclosure`	No
`cuota_informes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 25, 2026
- removedOutput schema / properties / plan / properties / precio_mes / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / plan / properties / precio_mes / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / token / properties / client / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / token / properties / client / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / usuario / properties / nombre / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / usuario / properties / nombre / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: it requires an authenticated account with the `cuenta:read` scope, and it lists the categories of account data returned.

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?

The description is compact and front-loads the returned data categories, with the auth requirement appended as a second sentence. No sentence is wasted, though the first sentence is a dense list rather than a clear action statement.

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?

Given the tool has no parameters, rich annotations, and an output schema, the description supplies the key missing context: what account data is exposed and that `cuenta:read` is required. It is nearly complete, lacking only explicit sibling differentiation for overlapping tools like planes.

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

Parameters4/5

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

The tool has zero parameters, so there are no parameter semantics to explain. The baseline for a parameterless tool is 4, and the description does not need to compensate for an input schema gap.

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

Purpose4/5

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

The description clearly identifies the resource being returned: the user's plan, report quota, available features, token scopes, usage limits, and useful URLs. It does not, however, distinguish this tool from siblings like planes or informe, which could overlap with the plan and report-quota aspects.

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?

It states a prerequisite ('Requiere cuenta (scope `cuenta:read`)') but gives no explicit when-to-use guidance or alternatives. The intended use is implied by the enumerated account data, but the agent is not told when to prefer this over planes or informe.

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

All Subastech — subastas judiciales de inmuebles (BOE) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?