Server Quality Checklist

Tool Scores

• bank_list_accountsD
  1.7/5.0
  Behavior2/5

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

  Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds only the phrase 'read-only response,' which repeats the annotation rather than adding new behavioral context such as pagination behavior, response format, or error handling.

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

  Conciseness2/5

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

  The description is a single short sentence, which is concise, but it lacks substance. It does not earn its place because it provides minimal value; a clearer, slightly longer description could be more useful without being verbose.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With two optional parameters, no output schema, and no parameter descriptions, the description is incomplete. It does not clarify what the tool returns, how pagination works, or any constraints, making it insufficient for an agent to fully understand the tool's behavior.

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

  Parameters1/5

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

  The schema has 0% description coverage, and the description does not explain the 'page' and 'pageSize' parameters. It fails to convey that these likely control pagination, leaving the agent without any clue about how to set them.

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

  Purpose2/5

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

  The description says 'Call Garanti Account Information and return its read-only response,' which is vague and doesn't clearly state that the tool lists accounts. It lacks a specific verb like 'list' or 'fetch' tied to the resource, and it doesn't differentiate from siblings like bank_get_balances or bank_list_transactions.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines1/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  There is no guidance on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent without enough information to decide between this and sibling tools.

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

• bank_get_balancesC
  2.6/5.0
  Behavior3/5

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

  With annotations already declaring readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds some context by explaining that the tool uses the Account Information product due to the lack of a separate balance API. This gives insight into the implementation but does not disclose return format, pagination behavior, or other relevant traits.

  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?

  The description is a single sentence, front-loaded with the purpose, and contains no filler. Every part earns its place, even though it is short.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool has no output schema, and the description does not explain what return data to expect (e.g., balance amounts, account identifiers, or formatting). It also lacks any mention of pagination despite page/pageSize parameters. For a simple read tool this is incomplete; the why clause about the Account Information product does not fill the gap.

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

  Parameters1/5

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

  Schema description coverage is 0%, so the description must compensate, but it provides no information about the page and pageSize parameters. The schema only gives type and numeric constraints, which do not add semantic meaning. The description says nothing about pagination or how these parameters affect results.

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

  Purpose3/5

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

  The description states a clear verb ('Read') and resource ('account information'), but it is vague about 'account information'—the tool name implies balances, yet the description does not mention balances explicitly. It also does not distinguish this from the sibling tool bank_list_accounts, which likely also reads account information.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It only explains that it uses the same Account Information product because no separate balance API exists, which is contextual background rather than usage direction. No exclusions or alternative tool references are given.

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

• bank_list_transactionsB
  3.1/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds a behavioral limitation ('No payment or transfer endpoint is available to this MCP') but does not disclose pagination behavior, auth requirements, or what data is returned. This is acceptable but not enriching.

  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 concise, with two sentences that each provide relevant information. The first sentence states the core function and scope, while the second adds a system limitation. It is appropriately sized and does not waste words, though the phrasing 'Call Garanti Account Transactions' is slightly awkward.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has 8 parameters and no output schema, the description is incomplete. It does not describe what the tool returns (e.g., a list of transactions), nor does it mention pagination, filtering behaviors, or the meaning of ambiguous parameters like direction or min/maxAmount. It relies heavily on annotations and schema, which are insufficient for this complexity.

  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 25%, with only 'ISO date-time' provided for from/to and no explanations for page, pageSize, direction, minAmount, maxAmount, or accountRef. The description mentions 'account and date range' which adds some meaning to three params, but the majority of parameters remain unexplained, and the description does not compensate for the low coverage.

  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 states the tool calls Garanti Account Transactions for an account and date range, which clearly identifies the resource and scoping. The verb 'Call' is somewhat generic, but combined with the name 'bank_list_transactions', the purpose is unambiguous and distinct from siblings like bank_get_balances.

  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?

  The description provides limited guidance on when to use this tool, only noting that no payment or transfer endpoint is available. It does not explicitly mention alternatives like bank_get_balances for balances or bank_list_accounts for accounts, so the usage context is only partially communicated.

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

• bank_test_connectionA
  4.1/5.0
  Behavior4/5

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

  The annotations already mark the tool as read-only and idempotent. The description adds meaningful context with 'The access token is never returned,' disclosing a security-relevant behavior that is not fully captured by the annotations. It does not contradict the annotations, and it offers a helpful guarantee about output behavior.

  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?

  The description is exceptionally concise: two short sentences that front-load the purpose and then add a key behavioral note. Every word earns its place, with no filler or repetition of schema/annotation information.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With no output schema, the description has the burden of explaining what the tool returns or how results are presented. It clearly states what is not returned (the token) but does not describe what is returned on success or failure. For a test tool, specifying outcome semantics (e.g., boolean, status message, exception behavior) would make it more complete.

  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 input schema has no parameters (100% schema coverage with an empty properties object). The baseline for zero parameters is 4, and there is no parameter information needed from the description. The description appropriately focuses on behavior rather than nonexistent inputs.

  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?

  The description clearly states the tool's purpose: 'Test Garanti OAuth client_credentials authentication.' The verb 'Test' plus the specific resource ('Garanti OAuth client_credentials authentication') distinguishes this from sibling data tools like bank_list_accounts, bank_get_balances, and bank_list_transactions. The added note about the access token never being returned further clarifies that this is a pure authentication check, not a credential retrieval.

  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?

  The description implies usage—this tool should be used to verify OAuth authentication—but it does not explicitly say when to use it versus alternatives or when not to use it. With sibling tools like bank_provider_status, more explicit guidance on when to choose this test over a provider status check would be beneficial.

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

• bank_provider_statusA
  4.2/5.0
  Behavior4/5

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

  With annotations already declaring this a read-only, idempotent, non-destructive operation, the description adds value by emphasizing that credentials are not exposed. This is a meaningful safety guarantee beyond the annotations. However, it does not describe the exact nature of the status output or any rate limits.

  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?

  The description is a single, concise sentence that directly states what the tool does and a key safety property. No wasted words.

  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?

  The tool is simple with no parameters and no output schema, but the description adequately conveys its purpose and safety. It does not detail the exact return format, but for a status-check tool, this is not a critical omission given the sibling tool context.

  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 the baseline score is 4. There is no schema coverage issue, and the description does not need to explain parameter behavior since none exist.

  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?

  The description clearly states the tool's function with a specific verb ('Show') and a specific resource ('Garanti API Store configuration status'), which distinguishes it from sibling tools focused on connections, accounts, balances, and transactions. The addition of 'without exposing credentials' also signals its unique safety scope.

  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?

  The usage context is implied by the name and description—it is for checking configuration status—but there is no explicit guidance on when to use this tool versus alternatives like bank_test_connection. No mention of exclusions or prerequisites.

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