Skip to main content
Glama

LiquiLens Failure Radar

RBI NBFC register search

universe_search
Read-onlyIdempotent

Search the RBI NBFC register. Supply q or a filter; a filter without q browses that slice. Registration does not establish creditworthiness.

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": "universe_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoname or CIN substring, case-insensitive
layerNoScale Based Regulation layer
limitNo
classificationNoexact register class, e.g. 'MFI' or 'HFC'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / classification / description
      Previous value: -"exact RBI register classification, e.g. 'MFI' or 'HFC'"New value: +"exact register class, e.g. 'MFI' or 'HFC'"
    • changedInput schema / properties / layer / description
      Previous value: -"Scale Based Regulation layer filter"New value: +"Scale Based Regulation layer"
    • removedInput schema / properties / limit / description
      Removed value: -"maximum rows to return"
    • changedInput schema / properties / q / description
      Previous value: -"case-insensitive substring of the registered name or CIN"New value: +"name or CIN substring, case-insensitive"
  2. Changed2 schema fields changed
    • changedInput schema / properties / classification / description
      Previous value: -"exact RBI classification as it appears in the register, e.g. 'MFI' or 'HFC'"New value: +"exact RBI register classification, e.g. 'MFI' or 'HFC'"
    • changedInput schema / properties / limit / description
      Previous value: -"maximum rows to return (default 20, capped at 50)"New value: +"maximum rows to return"
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two things beyond that: the filter-without-q browse semantics (a behavioral mode not visible in annotations) and the caveat that registration does not establish creditworthiness, which guards against misreading results as an endorsement. Result ordering, pagination behavior, and truncation beyond the limit are not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and followed by the invocation rule and the domain caveat. Every sentence carries distinct information and there is no filler or repetition of structured fields.

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?

For a 4-parameter, zero-required, read-only lookup with no output schema, the description covers what the tool is, how to invoke it in both modes, and how to interpret the result. The main remaining gap is that, with no output schema, nothing indicates the shape or size of the returned records or whether the limit truncates silently.

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

Parameters3/5

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

Schema coverage is 75%, so the schema already explains q as a name/CIN substring and classification as an exact register class, with limit bounded by min/max/default. The description's contribution is the interaction rule that a filter can be used without q to browse, which is genuine added meaning. It does not clarify limit semantics such as whether results are truncated or what ordering applies.

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 opens with a specific verb and resource: 'Search the RBI NBFC register.' That is unambiguous and clearly distinct from the sibling set, which consists of boards, evidence packs, and institution research tools rather than register lookups. It stops short of naming a sibling or contrasting scope, which keeps it from a 5.

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?

It states the two invocation modes explicitly: supply 'q' for a substring search, or supply a filter alone to browse that slice. That is real operational guidance an agent would otherwise have to infer. It does not say when to prefer this over a sibling like evidence_india or rbi_supervisory_tape, so no exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.